public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, liming.gao@intel.com,
	"announce@edk2.groups.io" <announce@edk2.groups.io>
Cc: "Guptha, Soumya K" <soumya.k.guptha@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"afish@apple.com" <afish@apple.com>,
	"leif@nuviainc.com" <leif@nuviainc.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Liran Alon <liran.alon@oracle.com>,
	Nikita Leshenko <nikita.leshchenko@oracle.com>
Subject: Re: [edk2-devel] EDK II Stable Tag release edk2-stable202002 completed
Date: Wed, 4 Mar 2020 19:23:59 +0100	[thread overview]
Message-ID: <c3e00022-220d-134f-1e9c-f333f8fe512d@redhat.com> (raw)
In-Reply-To: <738194b9a8b8430abaee9c2d886b4acc@intel.com>

Hi Liming,

On 03/04/20 10:03, Liming Gao wrote:

> 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.

Apologies for responding for the third time in a day, to the same call
from you :) It's not easy to keep all the sudden virtualization-related
feature request BZs :)

So please include the following three RFEs too, from Ard:
- https://bugzilla.tianocore.org/show_bug.cgi?id=2560
- https://bugzilla.tianocore.org/show_bug.cgi?id=2564
- https://bugzilla.tianocore.org/show_bug.cgi?id=2566

(So in total we have 6 ArmVirt / OVMF BZs planned, at this moment, for
the next stable tag: 2560, 2564, 2566 from Ard; 2390 and 2567 from Liran
and Nikita at Oracle; and 1512 from yours truly.)

Thank you!
Laszlo


  parent reply	other threads:[~2020-03-04 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04  9:03 EDK II Stable Tag release edk2-stable202002 completed Liming Gao
2020-03-04 14:43 ` Laszlo Ersek
2020-03-04 18:14 ` [edk2-devel] " Laszlo Ersek
2020-03-04 18:23 ` Laszlo Ersek [this message]
2020-03-05  5:53   ` [edk2-announce] " Liming Gao
2020-03-05 14:26     ` 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=c3e00022-220d-134f-1e9c-f333f8fe512d@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