public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <quic_llindhol@quicinc.com>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
	<devel@edk2.groups.io>, <gaoliming@byosoft.com.cn>,
	<discuss@edk2.groups.io>
Cc: "'Kinney, Michael D'" <michael.d.kinney@intel.com>,
	'Andrew Fish' <afish@apple.com>
Subject: Re: [edk2-devel] Soft Feature Freeze starts now for edk2-stable202311
Date: Thu, 9 Nov 2023 13:11:32 +0000	[thread overview]
Message-ID: <90fe2b9c-de7d-4716-8394-68d989c7125b@quicinc.com> (raw)
In-Reply-To: <50b1debb-9acf-4406-a587-3cc8886bb318@linaro.org>

-announce, +discuss

On 2023-11-09 12:02, Marcin Juszkiewicz wrote:
> W dniu 7.11.2023 o 01:59, gaoliming via groups.io pisze:
> 
>> Below is edk2-stable202311 tag planning Proposed Schedule
>>
>> Date (00:00:00 UTC-8) Description
>>
>> 2023-08-25 Beginning of development
>> 2023-11-06 Soft Feature Freeze
>> 2023-11-10 Hard Feature Freeze
>> 2023-11-24 Release
> 
> Can edk2-platforms and edk2-non-osi be tagged at same time as edk2? 
> There are projects outside which use both repositories to build firmware 
> for their use.
> 
> I was contacted with one of them as they had problem with SBSA Reference 
> Platform (sbsa-ref in QEMU, qemu-sbsa in TF-A, SbsaQemu in EDK2). Turned 
> out that their set of git repositories was far too much out of sync with 
> each other.
> 
> Having edk2-stable202311 tag in those 3 repositories show them exactly 
> which versions to use and make their life easier.

TL;DR: yes.

That is the long-term plan.
Perhaps approaching medium-term now.

But that requires pruning of platforms that are no longer actively 
maintained, and ongoing validation efforts on all platforms in 
edk2-platforms.

On the whole, tagging edk2-platforms at the same time as we tag the main 
repo is unlikely to be beneficial. We'll need to introduce a freeze of 
the platforms tree once the main repo stable tag is made and then wait 
for reports/updates from maintainers.
And implement a deprecation/archiving process for platforms where this 
does not happen in a timely fashion.
And I guess also tag the edk2-non-osi repo at the same time as the 
platforms repo.

And there's not a whole lot of us to work on this. And currently we're 
focusing on migrating to the copilot^Wgithub PR system for 
submissions/review.

/
     Leif



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



  reply	other threads:[~2023-11-09 13:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07  0:59 [edk2-devel] Soft Feature Freeze starts now for edk2-stable202311 gaoliming via groups.io
2023-11-09 12:02 ` Marcin Juszkiewicz
2023-11-09 13:11   ` Leif Lindholm [this message]
2023-11-22 11:11     ` [edk2-discuss] " Sami Mujawar
2023-11-22 12:26       ` Leif Lindholm
2023-11-22 13:21         ` Marcin Juszkiewicz
2023-11-22 13:49           ` Leif Lindholm
2023-11-22 23:45             ` Pedro Falcato

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=90fe2b9c-de7d-4716-8394-68d989c7125b@quicinc.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