* [RFC] EDK II stable tag releases
@ 2018-06-24 23:07 Kinney, Michael D
2018-06-25 15:23 ` Laszlo Ersek
0 siblings, 1 reply; 3+ messages in thread
From: Kinney, Michael D @ 2018-06-24 23:07 UTC (permalink / raw)
To: edk2-devel@lists.01.org
Hello,
This is a proposal for periodic stable tags on edk2 repositories.
The goal is to produce a stable tag for edk2 repositories every 3 months
with the initial proposed dates of 8/10/2018 and 11/16/2018. Each release
is preceded by a 2 week quiet period where only commits for critical bug
fixes are accepted.
When the stable tag release is completed, the release is tagged with the
following naming convention:
edk2-stable<4 digit year><2 digit month>
For example, the first 2 proposed tags would be:
edk2-stable201808
edk2-stable201811
The goal is to integrate major feature at the beginning of each 3 month
release cycle. Work through integration issues, smaller features, and
normal bug fixes through the remainder of the release cycle until the
start of the quiet period. The community focuses on testing and critical
bug fixes during the quiet period.
An EDK II Wiki page will be created to plan the development and testing
activities along with the dates associated for future EDK II stable tag
releases.
Please provide any feedback you have on this proposal.
Thanks,
Mike
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [RFC] EDK II stable tag releases
2018-06-24 23:07 [RFC] EDK II stable tag releases Kinney, Michael D
@ 2018-06-25 15:23 ` Laszlo Ersek
2018-06-28 10:41 ` Evan Lloyd
0 siblings, 1 reply; 3+ messages in thread
From: Laszlo Ersek @ 2018-06-25 15:23 UTC (permalink / raw)
To: Kinney, Michael D, edk2-devel@lists.01.org
On 06/25/18 01:07, Kinney, Michael D wrote:
> Hello,
>
> This is a proposal for periodic stable tags on edk2 repositories.
>
> The goal is to produce a stable tag for edk2 repositories every 3 months
> with the initial proposed dates of 8/10/2018 and 11/16/2018. Each release
> is preceded by a 2 week quiet period where only commits for critical bug
> fixes are accepted.
>
> When the stable tag release is completed, the release is tagged with the
> following naming convention:
>
> edk2-stable<4 digit year><2 digit month>
>
> For example, the first 2 proposed tags would be:
>
> edk2-stable201808
> edk2-stable201811
>
> The goal is to integrate major feature at the beginning of each 3 month
> release cycle. Work through integration issues, smaller features, and
> normal bug fixes through the remainder of the release cycle until the
> start of the quiet period. The community focuses on testing and critical
> bug fixes during the quiet period.
>
> An EDK II Wiki page will be created to plan the development and testing
> activities along with the dates associated for future EDK II stable tag
> releases.
>
> Please provide any feedback you have on this proposal.
I welcome it. :)
Thanks!
Laszlo
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [RFC] EDK II stable tag releases
2018-06-25 15:23 ` Laszlo Ersek
@ 2018-06-28 10:41 ` Evan Lloyd
0 siblings, 0 replies; 3+ messages in thread
From: Evan Lloyd @ 2018-06-28 10:41 UTC (permalink / raw)
To: Laszlo Ersek, Kinney, Michael D, edk2-devel@lists.01.org
> -----Original Message-----
> From: edk2-devel <edk2-devel-bounces@lists.01.org> On Behalf Of Laszlo
> Ersek
> Sent: 25 June 2018 16:23
> To: Kinney, Michael D <michael.d.kinney@intel.com>; edk2-
> devel@lists.01.org
> Subject: Re: [edk2] [RFC] EDK II stable tag releases
>
> On 06/25/18 01:07, Kinney, Michael D wrote:
> > Hello,
> >
> > This is a proposal for periodic stable tags on edk2 repositories.
> >
> > The goal is to produce a stable tag for edk2 repositories every 3
> > months with the initial proposed dates of 8/10/2018 and 11/16/2018.
> > Each release is preceded by a 2 week quiet period where only commits
> > for critical bug fixes are accepted.
> >
> > When the stable tag release is completed, the release is tagged with
> > the following naming convention:
> >
> > edk2-stable<4 digit year><2 digit month>
> >
> > For example, the first 2 proposed tags would be:
> >
> > edk2-stable201808
> > edk2-stable201811
> >
> > The goal is to integrate major feature at the beginning of each 3
> > month release cycle. Work through integration issues, smaller
> > features, and normal bug fixes through the remainder of the release
> > cycle until the start of the quiet period. The community focuses on
> > testing and critical bug fixes during the quiet period.
> >
> > An EDK II Wiki page will be created to plan the development and
> > testing activities along with the dates associated for future EDK II
> > stable tag releases.
> >
> > Please provide any feedback you have on this proposal.
>
> I welcome it. :)
>
> Thanks!
> Laszlo
[[Evan Lloyd]] I too think this is a good idea.
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-06-28 10:41 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-06-24 23:07 [RFC] EDK II stable tag releases Kinney, Michael D
2018-06-25 15:23 ` Laszlo Ersek
2018-06-28 10:41 ` Evan Lloyd
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox