From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, miki.demeter@intel.com
Cc: "announce@edk2.groups.io" <announce@edk2.groups.io>,
"discuss@edk2.groups.io" <discuss@edk2.groups.io>
Subject: Re: [edk2-devel] [IMPORTANT] February Release Reviews and Merges
Date: Thu, 9 Feb 2023 18:06:00 +0100 [thread overview]
Message-ID: <CAMj1kXFOxDzhzMxzMJtK4s--K2ipO-qjQj2UzHtQ1MnrEnSrnQ@mail.gmail.com> (raw)
In-Reply-To: <DS0PR11MB6445A64C90C3846FA00A20798DD89@DS0PR11MB6445.namprd11.prod.outlook.com>
On Thu, 9 Feb 2023 at 01:20, Demeter, Miki <miki.demeter@intel.com> wrote:
>
> Important Information About the February Release
>
>
>
> The Stewards are aware there has been an issue with getting patches reviewed and/or merged in a timely manner. The stewards are considering a delay to the February release to allow for these issues to be addressed.
>
>
>
> Please take the time to validate that your submissions to the email list fall into one of the two categories please contact me directly immediately and CC the mailing list
>
>
>
> [1] You have patches submitted to the mailing list requesting review with no response
>
>
>
> [2] You have patches submitted to the mailing list that have been reviewed but not merged for the February release
>
>
Allow me to point out that it is not the job of the maintainers to
review all submissions - their main responsibility is to shepherd
reviewed patches and get them merged. The community as a whole is
responsible for getting patches reviewed.
So can I add [3] here
[3] If you see unreviewed patches on the mailing list that are inside
your area of expertise, please go ahead and share your opinion, even
if you are not a maintainer, steward or affiliated with the Tiancore
project in another way.
prev parent reply other threads:[~2023-02-09 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 0:20 [IMPORTANT] February Release Reviews and Merges Demeter, Miki
2023-02-09 5:11 ` Chang, Abner
2023-02-09 17:01 ` [edk2-devel] " Demeter, Miki
2023-02-13 0:58 ` Chang, Abner
2023-02-09 17:06 ` Ard Biesheuvel [this message]
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=CAMj1kXFOxDzhzMxzMJtK4s--K2ipO-qjQj2UzHtQ1MnrEnSrnQ@mail.gmail.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