From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Michael Kinney <michael.d.kinney@intel.com>,
Andrew Fish <afish@apple.com>,
"Leif Lindholm (Linaro address)" <leif.lindholm@linaro.org>,
Stephano Cetola <stephano.cetola@intel.com>,
Brian Richardson <brian.richardson@intel.com>
Subject: Re: Soft Feature Freeze has started since Nov.1 for dk2-stable201811
Date: Wed, 7 Nov 2018 16:14:01 +0100 [thread overview]
Message-ID: <fb1cb6cb-cd76-159d-76b9-d09bcf7faf7e@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3659AB@SHSMSX104.ccr.corp.intel.com>
Hi,
On 11/07/18 02:12, Gao, Liming wrote:
> Hi, all
> https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning
> lists edk2-stable201811 tag planning. Now, we enter into Soft Feature
> Freeze phase. In this phase, the feature under review will not be
> allowed to be pushed. The patch review can continue without break.
> Here is edk2-stable201811 tag planning.
> 2018-08-15 Beginning of development
> 2018-11-01 Soft Feature Freeze
> 2018-11-08 Hard Feature Freeze
> 2018-11-15 Release
I don't think an announcement should be made like this, one week after
the fact. (If I missed the exact dates on yesterday's stewards' call,
then I apologize.)
If we are making the announcement about the Soft Feature Freeze on
2018-Nov-07, then the Soft Feature Freeze should start no earlier than
2018-Nov-08 or so. Certainly not retro-actively.
Perhaps we should push the schedule by one week.
I understand that will prevent the stable tag from being dropped
*exactly* three months after start of development (2018-Aug-15). I think
that should be fine. Nobody forces us to work in cycles of *exactly*
three months. (Even if we slipped over to December, that shouldn't be a
huge problem; we'd just call the tag "edk2-stable201812".) The workflow
itself is work-in-progress.
I realize that
<https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning>
has had the dates available all this time. But, the reason we make the
announcements in the first place is precisely that people don't keep
staring at that page.
(
For example, I reviewed and pushed 4 patches yesterday (on 2018-Nov-06):
1 e038bde2679b Revert "OvmfPkg/QemuVideoDxe: list "UnalignedIoInternal.h" in the INF file"
2 98856a724c2a Revert "OvmfPkg/QemuVideoDxe: VMWare SVGA device support"
3 438ada5aa5a1 Revert "OvmfPkg/QemuVideoDxe: Helper functions for unaligned port I/O."
4 328409ce8de7 Revert "OvmfPkg: VMWare SVGA display device register definitions"
which are the first four patches (out of five) from the following
series:
[edk2] [PATCH v2 0/5] OvmfPkg: simply use the Bochs interface for vmsvga
These reverts are arguably not bugfixes; they are preparation for
re-implementing a feature from scratch (the last patch in that series).
Thus, had I known we were already in the Soft Feature Freeze, I wouldn't
have pushed them, because the review was not complete before the soft
freeze start.
But I had just returned from a week (or more) of PTO, there was no
announcement on the list yet, and I didn't remember the wiki page.
(In the technical sense, the reverts are not disruptive, luckily; they
remove code that is dead anyway.)
)
This is my opinion at least -- I'm ready to be overruled, but I wanted
to voice it.
Thanks
Laszlo
next prev parent reply other threads:[~2018-11-07 15:14 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 [this message]
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
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=fb1cb6cb-cd76-159d-76b9-d09bcf7faf7e@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