Upcoming glibc-2.42 release

[Sachin Monga]

> Let's please not hurry this. It produced a CVE already.


Ok. I'll go with whatever community thinks is best. Let's drop it.
Lets cover other bugs(rawmemchr) also post-release.

Regards:
Sachin.


>>
>> 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
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20250702/3577e55a/attachment.htm>