From: Evan Lloyd <Evan.Lloyd@arm.com>
To: Laszlo Ersek <lersek@redhat.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [RFC] EDK II stable tag releases
Date: Thu, 28 Jun 2018 10:41:12 +0000 [thread overview]
Message-ID: <DB6PR08MB28066A06D7DC23F24AE19E6B8B4F0@DB6PR08MB2806.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <1dee3810-d70f-c378-2b3e-3d79a1cb4f91@redhat.com>
> -----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.
prev parent reply other threads:[~2018-06-28 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=DB6PR08MB28066A06D7DC23F24AE19E6B8B4F0@DB6PR08MB2806.eurprd08.prod.outlook.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