From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Upcoming glibc 2.33 freeze on January 4th --- Volunteer RM?
Date: Mon, 7 Dec 2020 21:32:25 -0500 [thread overview]
Message-ID: <ea1152bc-0297-03f6-b069-876e555843e6@redhat.com> (raw)
Community,
The upcoming glibc 2.33 will release on Monday Feburary 1st.
The release will enter freeze on Monday January 4th.
There are just 27 days until the freeze.
If we skip some of the holidays we have 16 days of active development.
Would anyone like to volunteer to be the release manager?
--
Cheers,
Carlos.
next reply other threads:[~2020-12-08 2:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 2:32 Carlos O'Donell [this message]
2020-12-14 12:54 ` Adhemerval Zanella
2020-12-14 22:56 ` Carlos O'Donell
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=ea1152bc-0297-03f6-b069-876e555843e6@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).