Retrospective on glibc 2.34 and glibc 2.35 release.

[Joseph Myers]

On Thu, 10 Feb 2022, Andreas K. Huettel via Libc-alpha wrote:

> * What is now the release date (with all related rules) moves one week
> earlier, and results in a release candidate *tarball* (with a tag) from
> the release branch.

The use of such a tarball is marginal - there's already supposed to be one 
at the start of the freeze for submission to the Translation Project.

The main thing is having a (long enough) proper freeze after which there 
are no major architecture-independent changes (ABI or otherwise) other 
than reverting the addition of any new features that have proved 
problematic at a late stage.

-- 
Joseph S. Myers
joseph@codesourcery.com