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

Hello,

The tag edk2-stable201808 has been created.

    https://github.com/tianocore/edk2/releases/tag/edk2-stable201808

    git clone -b edk2-stable201808 https://github.com/tianocore/edk2.git

The main EDK II Wiki page has been updated with a section
for edk2 stable tags.

    https://github.com/tianocore/tianocore.github.io/wiki/EDK-II

The quiet period has now ended. Thank you for your cooperation
and patience.  Normal commits can now be resumed.

Based on feedback from Laszlo I have also added an EDK II Release
Planning Wiki page with a proposed schedule for the next stable
tag and a placeholder for the list of Bugzilla entries for the
features that will be added and validated in this next stable tag.

    https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning

If you have ideas for features in the next stable tag, please enter
a Bugzilla for evaluation.  Please let us know if there are 
existing open Bugzilla entries that should be targeted at this next
stable tag.

Thanks,

Mike


             reply	other threads:[~2018-08-15 22:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15 22:28 Kinney, Michael D [this message]
2018-08-16 13:02 ` EDK II Stable Tag release edk2-stable201808 completed 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=E92EE9817A31E24EB0585FDF735412F5B8AC82AC@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