From: Joseph Myers <joseph@codesourcery.com>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Retrospective on glibc 2.34 and glibc 2.35 release.
Date: Thu, 10 Feb 2022 19:09:16 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2202101905190.196416@digraph.polyomino.org.uk> (raw)
In-Reply-To: <8024838.GXAFRqVoOG@pinacolada>
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
prev parent reply other threads:[~2022-02-10 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 14:57 Carlos O'Donell
2022-02-09 16:05 ` Joseph Myers
2022-02-10 1:09 ` Stafford Horne
2022-02-10 6:33 ` Siddhesh Poyarekar
2022-02-10 6:28 ` Siddhesh Poyarekar
2022-02-10 18:34 ` Andreas K. Huettel
2022-02-10 19:09 ` Joseph Myers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.22.394.2202101905190.196416@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dilfridge@gentoo.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).