public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
	"Laszlo Ersek <lersek@redhat.com> (lersek@redhat.com)"
	<lersek@redhat.com>,
	"Andrew Fish (afish@apple.com)" <afish@apple.com>,
	"Richardson, Brian" <brian.richardson@intel.com>
Subject: EDK II Stable Tag release edk2-stable201808 and quiet period starting today
Date: Wed, 8 Aug 2018 14:16:08 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B8ABD897@ORSMSX113.amr.corp.intel.com> (raw)

Hello,

I sent an RFC for review on EDK II stable tags.

https://lists.01.org/pipermail/edk2-devel/2018-June/026474.html

There were no objections and we would like to move forward
with the an EDK II Stable Tag release.  The original goal was
8/10/2018.  I have seen a request to move the stable tag
release out a few days.

I recommend we target 8/15/2018 and start a quiet period
on edk2/master starting today.  This means critical bug 
fixes only on edk2/master.  New features and large changes
should be held until the edk2-stable201808 tag is created.

Please use Bugzilla for the critical issues that must be
fixed before the tag is created.  

https://bugzilla.tianocore.org/

Thanks,

Mike
 


             reply	other threads:[~2018-08-08 14:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08 14:16 Kinney, Michael D [this message]
2018-08-14 15:11 ` EDK II Stable Tag release edk2-stable201808 and quiet period starting today Laszlo Ersek
2018-08-14 18:42   ` Kinney, Michael D
2018-08-15 16:52     ` Kinney, Michael D
2018-08-15  2:05   ` Zhang, Chao B
2018-08-15 11:13     ` 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=E92EE9817A31E24EB0585FDF735412F5B8ABD897@ORSMSX113.amr.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