public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: "announce@edk2.groups.io" <announce@edk2.groups.io>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: EDK II Stable Tag release edk2-stable201911 completed
Date: Mon, 2 Dec 2019 01:00:45 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E555017@SHSMSX104.ccr.corp.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 868 bytes --]

Hi, all

The tag edk2-stable201911 has been created. https://github.com/tianocore/edk2/releases/tag/edk2-stable201911
  git clone -b edk2-stable201911 https://github.com/tianocore/edk2.git

The tag edk2-stable201911 has been added into the main EDK II Wiki page.
  https://github.com/tianocore/tianocore.github.io/wiki/EDK-II

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

2020 edk2 stable tag planning has been added into wiki page. The detail planning will be discussed in edk2 mail list.
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 me know if there are existing open Bugzilla entries that should be targeted at this next stable tag.

Thanks
Liming

[-- Attachment #2: Type: text/html, Size: 3300 bytes --]

             reply	other threads:[~2019-12-02  1:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02  1:00 Liming Gao [this message]
2019-12-03 15:10 ` [edk2-devel] EDK II Stable Tag release edk2-stable201911 completed naitaku
2019-12-04  1:01   ` Liming Gao
2019-12-04 16:11     ` Ard Biesheuvel
2019-12-04 17:44       ` Leif Lindholm
2019-12-05  0:58         ` Liming Gao

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=4A89E2EF3DFEDB4C8BFDE51014F606A14E555017@SHSMSX104.ccr.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