From: Laszlo Ersek <lersek@redhat.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Andrew Fish <afish@apple.com>,
"Richardson, Brian" <brian.richardson@intel.com>,
"Cetola, Stephano" <stephano.cetola@intel.com>
Subject: Re: [edk2-wiki PATCH] release planning: announce the soft and hard feature freezes
Date: Fri, 9 Nov 2018 18:18:58 +0100 [thread overview]
Message-ID: <c52e5949-de61-3a84-af8c-f9356f0d9e34@redhat.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B8B2DACB@ORSMSX113.amr.corp.intel.com>
On 11/09/18 18:07, Kinney, Michael D wrote:
> Perhaps we should update Maintainers.txt with some lines
> that identify the developers that are currently assigned
> to the release/release planning role. That way, the Wiki
> can reference Maintainters.txt and we can update
> Maintainers.txt as the assignments change over time.
This is a great idea!
Recently, Liming posted a patch:
Maintainers.txt: Update EDK II Releases to EDK-II-Release-Planning wiki
it updates the "EDK II Releases" section in Maintainers.txt. The patch
hasn't been pushed yet.
Liming, can you submit a v2 of that patch, such that it adds you with an
"M" role for the "EDK II Releases" section? Then, I could update the
wiki patch using a reference to Maintainers.txt.
Thanks!
Laszlo
next prev parent reply other threads:[~2018-11-09 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 17:28 [edk2-wiki PATCH] release planning: announce the soft and hard feature freezes Laszlo Ersek
2018-11-09 10:05 ` Leif Lindholm
2018-11-09 15:09 ` Gao, Liming
2018-11-09 16:26 ` Laszlo Ersek
2018-11-09 17:07 ` Kinney, Michael D
2018-11-09 17:18 ` Laszlo Ersek [this message]
2018-11-10 14:20 ` Gao, Liming
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=c52e5949-de61-3a84-af8c-f9356f0d9e34@redhat.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