From: "Tian, Hot" <hot.tian@intel.com>
To: "Richardson, Brian" <brian.richardson@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
"Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-announce] Hard Feature Freeze starts from 2019-03-01(00:00:00 UTC-8) for edk2-stable201903
Date: Fri, 8 Mar 2019 14:30:36 +0000 [thread overview]
Message-ID: <97159AD15C0F454180C255F8DA66135535FE6367@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <80AC2BAA3152784F98F581129E5CF5AFBD7EEEAC@ORSMSX114.amr.corp.intel.com>
For this specific question from Laszlo, I do not have strong recommendation. Liming/Laszlo can work out a recommendation.
But looking at https://github.com/tianocore/tianocore.github.io/wiki/EDK-II, I do have recommendation to make UDK less prominent (e.g. remove "UDK Releases" section) as we've migrated to quarterly stable tag release model on edk2 master.
-----Original Message-----
From: Richardson, Brian
Sent: Friday, March 08, 2019 22:19
To: Tian, Hot <hot.tian@intel.com>; Tian, Hot <hot.tian@intel.com>; Laszlo Ersek <lersek@redhat.com>; Gao, Liming <liming.gao@intel.com>; edk2-devel@lists.01.org
Subject: RE: [edk2] [edk2-announce] Hard Feature Freeze starts from 2019-03-01(00:00:00 UTC-8) for edk2-stable201903
Hot: it looks like we need to revise the wiki page so the stable tag & release notes links are more prominent. Any recommendations on changes?
Thanks ... br
---
Brian Richardson -- Director, Firmware Ecosystem Development brian.richardson@intel.com -- @intel_brian (Twitter & WeChat) https://software.intel.com/en-us/meet-the-developers/evangelists/team/brian-richardson
-----Original Message-----
From: edk2-devel <edk2-devel-bounces@lists.01.org> On Behalf Of Tian, Hot
Sent: Friday, March 8, 2019 8:48 AM
To: Tian, Hot <hot.tian@intel.com>; Laszlo Ersek <lersek@redhat.com>; Gao, Liming <liming.gao@intel.com>; edk2-devel@lists.01.org
Subject: Re: [edk2] [edk2-announce] Hard Feature Freeze starts from 2019-03-01(00:00:00 UTC-8) for edk2-stable201903
I guess https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Notes is also for future release notes. Seems it's not listed on https://github.com/tianocore/tianocore.github.io/wiki/EDK-II.
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Tian, Hot
Sent: Friday, March 08, 2019 21:38
To: Laszlo Ersek <lersek@redhat.com>; Gao, Liming <liming.gao@intel.com>; edk2-devel@lists.01.org
Subject: Re: [edk2] [edk2-announce] Hard Feature Freeze starts from 2019-03-01(00:00:00 UTC-8) for edk2-stable201903
Hi Laszlo,
You can find the permanent release notes on https://github.com/tianocore/tianocore.github.io/wiki/EDK-II:
Under Stable Tags session: https://github.com/tianocore/edk2/releases/tag/edk2-stable201811
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning is for Future Release and Tag Planning.
Thanks,
Hot
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Laszlo Ersek
Sent: Friday, March 08, 2019 17:00
To: Gao, Liming <liming.gao@intel.com>; edk2-devel@lists.01.org
Subject: Re: [edk2] [edk2-announce] Hard Feature Freeze starts from 2019-03-01(00:00:00 UTC-8) for edk2-stable201903
Hi Liming,
On 03/01/19 09:57, Gao, Liming wrote:
> 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.
I meant to ask you about permanent links to already released stable tags, in the Wiki. For example, we have:
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Notes#edk2-stable201903-tag
but we don't seem to have one for the previous stable tag (edk2-stable201811). Which is strange because I remember that we collected the changes for that release too, in the wiki.
... Ah, I see it now. The problem is with Wiki commit 63a756e8a134
("edk2 wiki: remove edk2-stable201811 tag planning in EDK-II-Release-Planning", 2018-12-10). The content was removed completely.
For example, if I grep the wiki (currently at commit 664b82ca9684) for "id=1213", there are no hits. That means people cannot learn (or make references to) the fact, in the Wiki, that the edk2-stable201811 release fixed TianoCore#1213.
In my opinion, we should rather move that kind of content to a permanent Release Notes article in the Wiki.
Thanks
Laszlo
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2019-03-08 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 8:57 [edk2-announce] Hard Feature Freeze starts from 2019-03-01(00:00:00 UTC-8) for edk2-stable201903 Gao, Liming
2019-03-08 9:00 ` 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 [this message]
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=97159AD15C0F454180C255F8DA66135535FE6367@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