Upcoming glibc-2.42 release

[Adhemerval Zanella Netto]

On 02/07/25 09:23, Sam James wrote:
> Sachin Monga <smonga@linux.ibm.com> writes:
> 
>> Can we include fix for
>>
>> 1. https://sourceware.org/bugzilla/show_bug.cgi?id=33056
>>
>> 2. https://sourceware.org/bugzilla/show_bug.cgi?id=33060 ?
>>
>> I am sharing the patch in couple of minutes. Testing is ongoing. I
>> remeber reviewer needs objdump verification also.
> 
> My inclination is that it's too risky at this point (it already went
> wrong once to the tune of CVEs, I don't think we should rush it in now),
> but that isn't a veto either, just saying my opinion.
> 
> (I assume you mean the reapplication of the optimisations we reverted
> for those bugs.)
> 

Agree, and for such patches we can backport once the fixed implementations
are reviewed and tests on master.

>>
>>
>> Regards:
>> Sachin.
>>
>> On 12/06/25 7:34 pm, Andreas K. Huettel wrote:
>>> Hi all,
>>>
>>> unless someone else wants to step in, I'm going to take care of the upcoming
>>> release again.
>>>
>>> Suggested 6-week schedule, mostly just writing down how we've handled things
>>> in the past:
>>>
>>> - 20 June 2024: Soft freeze
>>>    * No *starting* of new features anymore
>>>    * Decisions on what goes still in and what goes not
>>>    * Review and addition of patches
>>>
>>> - 4 July 2025: Freeze
>>>    * Machine testing
>>>    * Bug fixes without large impact
>>>    * No ABI changes without RM discussion
>>>    * High risk bug fixes should be discussed on the list.
>>>
>>> - 18 July 2025: Hard freeze
>>>    * Only critically important or technically straightforward bug fixes
>>>
>>> - 1 Aug 2025 (or ideally a bit earlier): Release
>>>
>>> Cheers,
>>> Andreas
>>>