public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io
Cc: liming.gao@intel.com, Michael Kinney <michael.d.kinney@intel.com>,
	Stephano Cetola <stephano.cetola@intel.com>,
	Andrew Fish <afish@apple.com>,
	Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [edk2-devel] [edk2] Soft Feature Freeze starts today for edk2-stable201905
Date: Tue, 21 May 2019 23:05:08 +0200	[thread overview]
Message-ID: <a06be3de-2ad0-a4f7-a506-3813a0c67c7f@redhat.com> (raw)
In-Reply-To: <a9aa2c5f-ec6c-6d0b-208c-8038e2e85915@redhat.com>

On 05/21/19 23:01, Laszlo Ersek wrote:

>   https://github.com/lersek/edk2/wiki/SoftFeatureFreeze#what-is-the-soft-feature-freeze

Sorry, this link was wrong -- I got it from my browsers URL bar history,
and didn't notice it early enough. The right URL is:

https://github.com/tianocore/tianocore.github.io/wiki/SoftFeatureFreeze

and the content is identical:

>> The soft feature freeze is the beginning of the stabilization phase of
>> edk2's development process. By the date of the soft feature freeze,
>> developers must have sent their patches to the mailing list *and*
>> received positive maintainer reviews (Reviewed-by or Acked-by tags).
>> This means that features, and in particular non-trivial ones, must
>> have been accepted by maintainers before the soft freeze date.
>>
>> Between the soft feature freeze and the hard feature freeze,
>> previously reviewed and unit-tested features may be applied (or
>> merged) to the master branch, for integration testing. Feature
>> addition or enablement patches posted *or* reviewed after the soft
>> feature freeze will be delayed until after the upcoming stable tag.

Thanks
Laszlo

  reply	other threads:[~2019-05-21 21:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17  8:56 [edk2] Soft Feature Freeze starts today for edk2-stable201905 Liming Gao
2019-05-21 21:01 ` [edk2-devel] " Laszlo Ersek
2019-05-21 21:05   ` Laszlo Ersek [this message]
2019-05-22  8:28   ` Ni, Ray
2019-05-22  8:53     ` Laszlo Ersek
2019-05-22 12:09   ` Liming Gao
2019-05-22 13:04     ` Laszlo Ersek
2019-05-23  5:58       ` Liming Gao
2019-05-23 11:44         ` 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=a06be3de-2ad0-a4f7-a506-3813a0c67c7f@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