public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming via groups.io" <gaoliming=byosoft.com.cn@groups.io>
To: <devel@edk2.groups.io>, <michael.d.kinney@intel.com>,
	<announce@edk2.groups.io>
Cc: "'Andrew Fish'" <afish@apple.com>,
	<leif.lindholm@oss.qualcomm.com>,
	"'Ard Biesheuvel'" <ardb@kernel.org>
Subject: 回复: [edk2-devel] Soft Feature Freeze starts now for edk2-stable202502
Date: Tue, 4 Feb 2025 10:04:32 +0800	[thread overview]
Message-ID: <059d01db76a9$23272480$69756d80$@byosoft.com.cn> (raw)
In-Reply-To: <CO1PR11MB49293F597417B58E18987972D2F52@CO1PR11MB4929.namprd11.prod.outlook.com>

Mike:
 Thanks. The milestone is helpful for the stable tag release process.

Thanks
Liming
> -----邮件原件-----
> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Michael D
> Kinney via groups.io
> 发送时间: 2025年2月4日 2:28
> 收件人: gaoliming <gaoliming@byosoft.com.cn>; devel@edk2.groups.io;
> announce@edk2.groups.io
> 抄送: 'Andrew Fish' <afish@apple.com>; leif.lindholm@oss.qualcomm.com;
> 'Ard Biesheuvel' <ardb@kernel.org>; Kinney, Michael D
> <michael.d.kinney@intel.com>
> 主题: Re: [edk2-devel] Soft Feature Freeze starts now for edk2-stable202502
> 
> Hi Liming,
> 
> The Milestone "edk2-stable202502" has been added for PRs, so
> any PR that should be considered for this release should be
> tagged with that Milestone.  That will make it easier to track
> progress through the soft and hard freeze to know when all
> PRs targeted for this release are either merged or closed.
> 
> Thanks,
> 
> Mike
> 
> From: gaoliming <gaoliming@byosoft.com.cn>
> Sent: Sunday, February 2, 2025 11:57 PM
> To: devel@edk2.groups.io; announce@edk2.groups.io
> Cc: 'Andrew Fish' <afish@apple.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>; leif.lindholm@oss.qualcomm.com; 'Ard
> Biesheuvel' <ardb@kernel.org>
> Subject: Soft Feature Freeze starts now for edk2-stable202502
> 
> Hi, all
> 
>   We enter into Soft Feature Freeze phase now. In this phase,
> the feature under review will not be allowed to be pushed. The feature
> passed review can still be merged.
> 
>   The patch review can continue without break in edk2 community. If the
> patch is under review process, and plans to catch this stable tag, the
> patch contributor need to send the request in edk2 mail list. If the patch
> is submitted after Soft Feature Freeze, and plans to catch this stable tag,
> Please send the request in edk2 mail list and notify edk2 community, so the
> community know this patch target and give the feedback.
> 
>   To avoid the unnecessary changes to be merged in edk2 stable tag release,
> all edk2 maintainers' write access will be temporarily disabled until stable
> tag is released on 02-21. That means edk2 maintainer can't set push label in
> pull request after soft feature freeze starts.
> 
>   If the change wants to catch this stable tag 202502, please follow above
> rules, then send the pull request to mailto:gaoliming@byosoft.com.cn or
> mailto:michael.d.kinney@intel.com.
> 
>   We will help merge the code change in soft feature freeze and hard feature
> freeze phase.
> 
> Below is edk2-stable202502 tag planning Proposed Schedule
> Date (00:00:00 UTC-8) Description
> 2024-11-22 Beginning of development
> 2025-02-03 Soft Feature Freeze
> 2025-02-07 Hard Feature Freeze
> 2025-02-21 Release
> 
> Thanks
> Liming
> 
> 
> 
> 
> 





-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121079): https://edk2.groups.io/g/devel/message/121079
Mute This Topic: https://groups.io/mt/110985396/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



      reply	other threads:[~2025-02-04  2:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03  7:56 [edk2-devel] Soft Feature Freeze starts now for edk2-stable202502 gaoliming via groups.io
2025-02-03 18:28 ` Michael D Kinney via groups.io
2025-02-04  2:04   ` gaoliming via groups.io [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='059d01db76a9$23272480$69756d80$@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