public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Noah Goldstein <goldstein.w.n@gmail.com>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>
Cc: adhemerval.zanella@linaro.org, siddhesh@sourceware.org,
	 libc-alpha@sourceware.org, carlos@redhat.com
Subject: Re: freeze for the upcoming glibc 2.38 release
Date: Mon, 10 Jul 2023 11:06:10 -0500	[thread overview]
Message-ID: <CAFUsyfLvOw04ze=q5JfgbWBfxfgpg5j58_mfqWsVOyp1-KRSVA@mail.gmail.com> (raw)
In-Reply-To: <1817162.X513TT2pbd@pinacolada>

On Thu, Jul 6, 2023 at 1:29 PM Andreas K. Huettel via Libc-alpha
<libc-alpha@sourceware.org> 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? ##
>
>   Anything else?

I would like to make sure any necessary follow ups for tuning the
`non_temporal_threshold` on X86 machines gets into 2.38.
>
>
> - 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)

  parent reply	other threads:[~2023-07-10 16:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 18:28 Andreas K. Huettel
2023-07-06 18:43 ` Xi Ruoyao
2023-07-08 17:42   ` Andreas K. Huettel
2023-07-09 12:25     ` Xi Ruoyao
2023-07-07  7:29 ` Paul Zimmermann
2023-07-08 17:44   ` Andreas K. Huettel
2023-07-09  7:12     ` Paul Zimmermann
2023-07-07 10:18 ` Siddhesh Poyarekar
2023-07-08 17:46   ` Andreas K. Huettel
2023-07-07 12:12 ` Adhemerval Zanella Netto
2023-07-07 21:21   ` Andreas K. Huettel
2023-07-08 17:51     ` Andreas K. Huettel
2023-07-07 21:40   ` Andreas K. Huettel
2023-07-08 17:48     ` Andreas K. Huettel
2023-07-10 15:45       ` Adhemerval Zanella Netto
2023-07-10 16:06 ` Noah Goldstein [this message]
2023-07-13 21:35   ` Andreas K. Huettel
2023-07-14  2:24     ` Noah Goldstein

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='CAFUsyfLvOw04ze=q5JfgbWBfxfgpg5j58_mfqWsVOyp1-KRSVA@mail.gmail.com' \
    --to=goldstein.w.n@gmail.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=dilfridge@gentoo.org \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@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).