From: "Gao, Liming" <liming.gao@intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: [edk2-announce] Hard Feature Freeze starts from 2019-03-01(00:00:00 UTC-8) for edk2-stable201903
Date: Fri, 1 Mar 2019 08:57:39 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3F87B2@SHSMSX104.ccr.corp.intel.com> (raw)
Hi, all
Today, we enter into Hard Feature Freeze phase until edk2-stable201903 tag is created at 2019-03-08. In this phase, there is no feature to be pushed. The bug fix is still allowed.
Thanks
Liming
>-----Original Message-----
>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Gao,
>Liming
>Sent: Friday, February 22, 2019 10:26 PM
>To: edk2-devel@lists.01.org
>Subject: [edk2] [edk2-announce] Soft Feature Freeze starts today for edk2-
>stable201903
>
>Hi, all
> https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-
>Planning lists edk2-stable201903 tag planning. Now, we enter into Soft
>Feature Freeze phase. In this phase, the feature without Reviewed-by or
>Acked-by tags will be delayed after the upcoming stable tag. The patch review
>can continue without break. Below is edk2-stable201903 tag planning.
>
>2019-03-08 Beginning of development
>2019-02-22 Soft Feature Freeze
>2019-03-01 Hard Feature Freeze
>2019-03-08 Release
>
>Thanks
>Liming
>
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org
>https://lists.01.org/mailman/listinfo/edk2-devel
next reply other threads:[~2019-03-01 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 8:57 Gao, Liming [this message]
2019-03-08 9:00 ` [edk2-announce] Hard Feature Freeze starts from 2019-03-01(00:00:00 UTC-8) for edk2-stable201903 Laszlo Ersek
2019-03-08 13:37 ` Tian, Hot
2019-03-08 13:48 ` Tian, Hot
2019-03-08 14:18 ` Richardson, Brian
2019-03-08 14:30 ` Tian, Hot
2019-03-08 15:20 ` Laszlo Ersek
2019-03-08 15:56 ` Gao, Liming
2019-03-08 21:32 ` Richardson, Brian
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=4A89E2EF3DFEDB4C8BFDE51014F606A14E3F87B2@SHSMSX104.ccr.corp.intel.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