From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Status and plans for glibc 2.37 release on February 1st 2023
Date: Sat, 31 Dec 2022 13:11:13 -0500 [thread overview]
Message-ID: <5468f23f-8a0c-3957-fc00-1b4f06f003fc@redhat.com> (raw)
Community,
I am volunteering as the release manager for glibc 2.37.
Starting with glibc 2.38 I would like to offer my time to mentor
someone who would like to be a release manager for 2.38 (releasing
August 1st 2023). I will make this offer again after the 2.37
release.
Looking at the calendar the plan looks like this:
- Monday patch review switches to reviewing critical bug list and
ABI issues.
- Restarts January 9th.
- January 2-6 is slushy ABI freeze.
- No new ABI additions.
- ABI corrections should be reviewed, RM approval not required.
- Status of _r_debug COPY relocations is something we should look at.
https://patchwork.sourceware.org/project/glibc/list/?series=13978
- Liberal bug fixes.
- Status of pthread cond missed wakup is critical for this release.
- I will be making specific time to review the current status.
https://patchwork.sourceware.org/project/glibc/list/?series=13224
https://patchwork.sourceware.org/project/glibc/list/?series=12876
- January 9-31st is hard ABI freeze.
- Bug fixing.
- No ABI changes without RM discussion.
- Higher risk bug fixes should be discussed with community.
- February 1st
- glibc 2.37 release.
Please raise any concerns you have with this plan.
--
Cheers,
Carlos.
next reply other threads:[~2022-12-31 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 18:11 Carlos O'Donell [this message]
2023-01-03 14:28 ` Siddhesh Poyarekar
2023-01-03 15:23 ` Adhemerval Zanella Netto
2023-01-03 18:50 ` 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=5468f23f-8a0c-3957-fc00-1b4f06f003fc@redhat.com \
--to=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).