freeze for the upcoming glibc 2.38 release

[Andreas K. Huettel]

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? ##

  Anything else?


- July 12-31, "hard ABI freeze"
  * Noncritical bug fixes.
  * No ABI changes without RM discussion.
  * High risk bug fixes should be discussed on the list.


- August 1
  * glibc 2.38 release

  
If you have any comments or objections, please reply to the list.
  
Cheers,
Andreas


-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 981 bytes
Desc: This is a digitally signed message part.
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20230706/0ce73e41/attachment.sig>