Re: freeze for the upcoming glibc 2.38 release

[Siddhesh Poyarekar <siddhesh@sourceware.org>]

On 2023-07-06 14:28, Andreas K. Huettel wrote:
> Hello everyone,
> 
> as you may have already heard I'm volunteering as release manager for the
> upcoming glibc 2.38.
> 
> We follow approximately the same schedule as last time.
> 
> 
> - July 6-11, "slushy ABI freeze"
>    * No new ABI additions.
>    * ABI corrections should be reviewed, RM approval not required.
>    * Avoid any changes that require action by the ports (including all
>      that require ulps regeneration)
>    * Bug fixes.
>    * Monday patch review switches to reviewing critical bug list and
>      ABI issues.
> 
>    We still have two "desirables" on the wiki page,
>    * "Add clone3 support for multiple architectures" - can we wrap this up
>      safely next week?
>      https://patchwork.sourceware.org/project/glibc/list/?series=16730
>    * "Flip defaults for some security-relevant build configuration flags"
>      https://patchwork.sourceware.org/project/glibc/list/?series=21908
>      The series consists of 4 patches. 2 (stack-protector-strong), 3
>      (bind-now) and 4 (disable-crypt) should be uncontroversial.
>      ## The list thread on 1 (autoconf-2.71) ended without a clear
>         conclusion. What's the status here? ##

I addressed Joseph's concern about sysdep configure and preconfigure 
snippets in v2; I clarified in the git commit log that the sysdep 
scripts did change but they were all trivial transformations that do not 
affect functionality.

Thanks,
Sid