public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <lersek@redhat.com>
Subject: 回复: [edk2-devel] edk2-stable202102 tag planning
Date: Sat, 20 Feb 2021 13:37:45 +0800	[thread overview]
Message-ID: <007d01d7074a$83ef6e80$8bce4b80$@byosoft.com.cn> (raw)
In-Reply-To: <12f5aa44-90a9-48af-fb60-23c0bddad8dc@redhat.com>

Laszlo:
  For 2507, I don't get the work plan for it. So, I will remove it for this stable tag together with 3132. 

Thanks
Liming
> -----邮件原件-----
> 发件人: bounce+27952+71860+4905953+8761045@groups.io
> <bounce+27952+71860+4905953+8761045@groups.io> 代表 Laszlo Ersek
> 发送时间: 2021年2月20日 6:18
> 收件人: Liming Gao (Byosoft address) <gaoliming@byosoft.com.cn>
> 抄送: edk2-devel-groups-io <devel@edk2.groups.io>
> 主题: [edk2-devel] edk2-stable202102 tag planning
> 
> Hi Liming,
> 
> quickly opening the BZs listed under
> 
> https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planni
> ng#proposed-features
> 
> I find the following two tickets are not in RESOLVED status yet:
> 
>   CryptoPkg/OpensslLib: Add native instruction support for X64
>   https://bugzilla.tianocore.org/show_bug.cgi?id=2507
> 
>   OVMF RFE: VCPU hot-unplug with SMI
>   https://bugzilla.tianocore.org/show_bug.cgi?id=3132
> 
> BZ#3132 is going to miss edk2-stable202102, so I was about to delete
> that entry myself, from this list.
> 
> However, I noticed BZ#2507 too, and I don't know the status of that ticket.
> 
> I think it would be better to remove all tickets in one go that need to
> be postponed to the next development cycle, at this point
> 
> Could you please ask the owners of #2507 about their status / plans?
> 
> And then, can you please remove #3132 (and, if needed, #2507 as well)
> from the feature list?
> 
> Thanks!
> Laszlo
> 
> 
> 
> 
> 




      reply	other threads:[~2021-02-20  5:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 22:17 edk2-stable202102 tag planning Laszlo Ersek
2021-02-20  5:37 ` gaoliming [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='007d01d7074a$83ef6e80$8bce4b80$@byosoft.com.cn' \
    --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