Re: [edk2-discuss] [edk2-devel] Soft Feature Freeze starts now for edk2-stable202311

["Sami Mujawar" <sami.mujawar@arm.com>]

Hi Leif,

Please see my response inline marked [SAMI].

Regards,

Sami Mujawar

On 09/11/2023, 13:12, "discuss@edk2.groups.io <mailto:discuss@edk2.groups.io> on behalf of Leif Lindholm via groups.io" <discuss@edk2.groups.io <mailto:discuss@edk2.groups.io> on behalf of quic_llindhol=quicinc.com@groups.io <mailto:quicinc.com@groups.io>> wrote:


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

[SAMI] The proposal above looks good to me. 
This may be slightly off topic, but can we also enable edk2-platform upstream CI as well, please? This would be helpful to catch issues much earlier. 
There have been several instances where changes in edk2 repo have broken platforms in edk2-platforms and this has gone unnoticed until someone tried to build that platform.
I understand the proposal above requires maintainers to build and test the platforms once the platform freeze is announced. 
However, I think having an upstream edk2-platforms CI may reduce some of the burden and last-minute rush for the maintainers.
Please let me know your thoughts.
[/SAMI] 

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 (#111600): https://edk2.groups.io/g/devel/message/111600
Mute This Topic: https://groups.io/mt/102746762/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-