public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
	"Zeng, Star" <star.zeng@intel.com>,
	 Leif Lindholm <leif.lindholm@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Cetola, Stephano" <stephano.cetola@intel.com>,
	"Richardson, Brian" <brian.richardson@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: Soft Feature Freeze has started since Nov.1 for dk2-stable201811
Date: Thu, 8 Nov 2018 14:09:50 +0100	[thread overview]
Message-ID: <07518c3e-139a-f7e3-6a50-18e88da42422@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3665ED@SHSMSX104.ccr.corp.intel.com>

On 11/08/18 06:39, Gao, Liming wrote:

> Laszlo: Thanks for your feedback. We will send the separate announce
> mail ahead of the feature freeze date for next release cycle. And, I
> suggest to update SoftFeatureFreeze and HardFeatureFreeze wiki page
> with the announce mail requirement. For this release, I would like to
> dry run this process. So, I will send another  announcement for Hard
> Feature Freeze today.

I'm happy to update these wiki pages. Whom should I identify in the
articles as the expected sender(s) of the announcements?

Thanks!
Laszlo


  reply	other threads:[~2018-11-08 13:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07  1:12 Soft Feature Freeze has started since Nov.1 for dk2-stable201811 Gao, Liming
2018-11-07 15:14 ` Laszlo Ersek
2018-11-07 15:38   ` Leif Lindholm
2018-11-07 19:13     ` Laszlo Ersek
2018-11-08  2:02       ` Zeng, Star
2018-11-08  5:39         ` Gao, Liming
2018-11-08 13:09           ` Laszlo Ersek [this message]
2018-11-08 13:57             ` Gao, Liming
2018-11-08 17:13               ` Laszlo Ersek
2018-11-09 16:46       ` [urgent] " Laszlo Ersek
2018-11-09 18:08         ` Leif Lindholm
2018-11-09 19:08         ` Phil Dennis-Jordan
2018-11-09 19:32           ` Laszlo Ersek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=07518c3e-139a-f7e3-6a50-18e88da42422@redhat.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox