Status and plans for glibc 2.37 release on February 1st 2023

[Siddhesh Poyarekar]

On 2022-12-31 13:11, Carlos O'Donell via Libc-alpha wrote:
> Looking at the calendar the plan looks like this:
> 
> - Monday patch review switches to reviewing critical bug list and
>    ABI issues.
>   - Restarts January 9th.
> 
> - January 2-6 is slushy ABI freeze.
>   - No new ABI additions.
>   - ABI corrections should be reviewed, RM approval not required.
>    - Status of _r_debug COPY relocations is something we should look at.
>      https://patchwork.sourceware.org/project/glibc/list/?series=13978
>   - Liberal bug fixes.
>    - Status of pthread cond missed wakup is critical for this release.
>      - I will be making specific time to review the current status.
>        https://patchwork.sourceware.org/project/glibc/list/?series=13224
>        https://patchwork.sourceware.org/project/glibc/list/?series=12876
> 
> - January 9-31st is hard ABI freeze.
>   - Bug fixing.
>   - No ABI changes without RM discussion.
>   - Higher risk bug fixes should be discussed with community.
> 
> - February 1st
>   - glibc 2.37 release.

I'd like to have the _FORTIFY_SOURCE documentation[1] included in 2.37. 
I've added it as a blocker in the Release wiki page[2].

Thanks,
Sid

[1] 
https://patchwork.sourceware.org/project/glibc/patch/20221222160403.4151387-1-siddhesh@sourceware.org/
[2] https://sourceware.org/glibc/wiki/Release/2.37#Release_blockers.3F