From: Joseph Myers <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Retrospective on glibc 2.34 and glibc 2.35 release.
Date: Wed, 9 Feb 2022 16:05:31 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2202091602260.136717@digraph.polyomino.org.uk> (raw)
In-Reply-To: <a42078c5-dd0e-a59d-722c-3647d5709283@redhat.com>
On Wed, 9 Feb 2022, Carlos O'Donell via Libc-alpha wrote:
> In order to support these ABI changes I wonder if we don't need a specific
> window within the release like "Month 1: ABI" where we focus on this theme
> of getting new ABIs into the first month of development? There is a similarity
> here with respect to gcc's staged development.
I don't think we need such a short period for getting new ABIs in. Five
months for general development and one month for stablization and testing
should be fine if we return to having a proper release freeze with no
major architecture-independent changes, whether or not they affect ABIs,
in at least the last two weeks of the freeze (unless significant problems
with a new ABI are discovered late, in which case the normal expectation
should be to remove it from the release and reconsider in fixed form for
the next release).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-02-09 16:05 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 [this message]
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
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.2202091602260.136717@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--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).