public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney via groups.io" <michael.d.kinney=intel.com@groups.io>
To: "gaoliming@byosoft.com.cn" <gaoliming@byosoft.com.cn>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"announce@edk2.groups.io" <announce@edk2.groups.io>
Cc: 'Ard Biesheuvel' <ardb@kernel.org>,
	"Kubacki, Michael" <michael.kubacki@microsoft.com>,
	"leif.lindholm@oss.qualcomm.com" <leif.lindholm@oss.qualcomm.com>,
	'Andrew Fish' <afish@apple.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [edk2-announce] Hard Feature Freeze starts now for edk2-stable202502
Date: Fri, 7 Feb 2025 16:58:50 +0000	[thread overview]
Message-ID: <CO1PR11MB49296A7CB35AECDC58BAC1C0D2F12@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <022a01db796f$c19d64d0$44d82e70$@byosoft.com.cn>

Hi Liming,

During the soft/hard freeze period, most developers do not have
permissions to set the milestone.


Email is one way to request a PR for the next stable tag.

Another is to add a comment to the PR requesting the PR be 
considered for the next PR.

If the stewards approve the request, then the release owner can
set the milestone.

Thanks,

Mike


> -----Original Message-----
> From: announce@edk2.groups.io <announce@edk2.groups.io> On Behalf Of
> gaoliming via groups.io
> Sent: Friday, February 7, 2025 6:51 AM
> To: devel@edk2.groups.io; announce@edk2.groups.io
> Cc: 'Ard Biesheuvel' <ardb@kernel.org>; Kinney, Michael D
> <michael.d.kinney@intel.com>; Kubacki, Michael
> <michael.kubacki@microsoft.com>; leif.lindholm@oss.qualcomm.com;
> 'Andrew Fish' <afish@apple.com>
> Subject: [edk2-announce] Hard Feature Freeze starts now for edk2-
> stable202502
> 
> Hi, all
> 
>   Now, we enter into Hard Feature Freeze phase until edk2-stable202502
> tag
> is created at 2025-02-21. In this phase, there is no feature to be
> pushed.
> The critical bug fix or the approved change is still allowed.
> 
> 
> 
>   If PR is submitted after Hard Feature Freeze, and plans to catch this
> stable tag, please set its milestone to edk2-stable202502, and also
> send the
> mail in the mail list cc to the Tianocore Stewards.
> 
> 
> 
> Below is edk2-stable202502 tag planning.
> 
> https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-
> Plannin
> g
> 
> 
> 
> 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 (#121112): https://edk2.groups.io/g/devel/message/121112
Mute This Topic: https://groups.io/mt/111055629/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2025-02-07 16:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 14:51 [edk2-devel] Hard Feature Freeze starts now for edk2-stable202502 gaoliming via groups.io
2025-02-07 16:58 ` Michael D Kinney via groups.io [this message]
2025-02-10  6:29 ` Zeng, Star via groups.io

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=CO1PR11MB49296A7CB35AECDC58BAC1C0D2F12@CO1PR11MB4929.namprd11.prod.outlook.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