From: "Gao, Liming" <liming.gao@intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Edk2 2019 Q1 stable tag planning is added into EDK-II-Release-Planning wiki
Date: Fri, 9 Nov 2018 14:25:23 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E368220@SHSMSX104.ccr.corp.intel.com> (raw)
Hi, all
Next edk2 stable tag planning has been added into EDK-II-Release-Planning wiki https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning. Please review the proposed schedule. The proposed features are not finalized. If you know any feature will be ready, please propose to add it into the feature scope.
edk2-stable201903 tag planning
Proposed Schedule
Date
Description
2018-11-15
Beginning of development
2019-02-22
Soft Feature Freeze<https://github.com/tianocore/tianocore.github.io/wiki/SoftFeatureFreeze>
2019-03-01
Hard Feature Freeze<https://github.com/tianocore/tianocore.github.io/wiki/HardFeatureFreeze>
2019-03-08
Release
Proposed Features
* Python 3 migration<https://bugzilla.tianocore.org/show_bug.cgi?id=55>
* Add MSFT toolchain support to BaseStackCheckLib<https://bugzilla.tianocore.org/show_bug.cgi?id=1239>
* BaseTool Suggestions for improving building performance<https://bugzilla.tianocore.org/show_bug.cgi?id=1288>
* Delete IPv4 only TCP/iSCSI/PXE drivers in MdeModulePkg<https://bugzilla.tianocore.org/show_bug.cgi?id=1278>
* Remove EdkShellPkg from edk2/master<https://bugzilla.tianocore.org/show_bug.cgi?id=1107>
* Remove EdkShellBinPkg from edk2/master<https://bugzilla.tianocore.org/show_bug.cgi?id=1108>
* BaseTools: Support Array and C code style initialization in Structure PCD<https://bugzilla.tianocore.org/show_bug.cgi?id=1292>
* TBD Bugzilla List
Thanks
Liming
next reply other threads:[~2018-11-09 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 14:25 Gao, Liming [this message]
2018-11-12 10:57 ` Edk2 2019 Q1 stable tag planning is added into EDK-II-Release-Planning wiki Laszlo Ersek
2018-11-27 11:34 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14E368220@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