public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"'announce@edk2.groups.io'" <announce@edk2.groups.io>
Cc: "leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
	"afish@apple.com" <afish@apple.com>,
	"Laszlo Ersek (lersek@redhat.com)" <lersek@redhat.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: EDK II Stable Tag edk2-stable201905 will be created based on commit 20d2e5a125e34fc8501026613a71549b2a1a3e54
Date: Thu, 6 Jun 2019 07:32:38 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E46CBAA@SHSMSX104.ccr.corp.intel.com> (raw)

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

Hi, all

Today, I review all patches in edk2 mail list. There is no patches for EDK II Stable Tag edk2-stable201905. Based on edk2-stable201905 tag planning, it will be released at 2019-06-06. So, I plan to create edk2-stable201905 based on current edk2 trunk (the latest commit https://github.com/tianocore/edk2/commit/20d2e5a125e34fc8501026613a71549b2a1a3e54 CryptoPkg/OpensslLib: fix build break caused by missing library) on UTC - 8 00:00 of 2019-06-06. If you have any comments, please reply the mail. If no concern or objection, I will create tag and send another announce mail that edk2-stable201905 is completed and normal commit is resumed.

Thanks
Liming


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

             reply	other threads:[~2019-06-06  7:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06  7:32 Liming Gao [this message]
2019-06-06  7:49 ` EDK II Stable Tag edk2-stable201905 will be created based on commit 20d2e5a125e34fc8501026613a71549b2a1a3e54 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=4A89E2EF3DFEDB4C8BFDE51014F606A14E46CBAA@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