From: Carlos O'Donell <carlos@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
libc-alpha <libc-alpha@sourceware.org>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
Rajalakshmi Srinivasaraghavan <rajis@linux.vnet.ibm.com>,
DJ Delorie <dj@redhat.com>, Stefan Liebler <stli@linux.ibm.com>,
"Andreas K. Huettel" <dilfridge@gentoo.org>,
Sam James <sam@gentoo.org>,
Michael Hudson-Doyle <michael.hudson@canonical.com>,
Andreas Schwab <schwab@suse.de>
Subject: Re: Volunteer for release manager for glibc 2.38?
Date: Thu, 23 Mar 2023 09:37:05 -0400 [thread overview]
Message-ID: <258293c4-1cf4-7825-7de7-5fa56dbf4ff6@redhat.com> (raw)
In-Reply-To: <3e44ff1c-9e3b-34f7-ee5a-b73438f875bd@linaro.org>
On 3/2/23 11:49, Adhemerval Zanella Netto wrote:
>
>
> On 01/03/23 12:30, Carlos O'Donell via Libc-alpha wrote:
>> Community,
>>
>> On August 1st 2023, in 5 months, we want to release glibc 2.38.
>>
>> I am looking for a volunteer who would like to be the release
>> manager for the release.
>>
>> The release manager process is documented here:
>> https://sourceware.org/glibc/wiki/Release
>>
>> I am offering to mentor anyone who wants to learn the upstream
>> release manager process, and help the community run the release.
>>
>> This mentorship can be in the form of email, IRC, matrix, video,
>> etc, whatever you might need to support running the release
>> process.
>>
>> Every time we have a new person run through the process it gets
>> better.
>>
>> The new perspective and opinions make the process better :-)
>>
>
> Hi Carlos,
>
> I can work on this for next release if no one else want to step
> in.
I haven't had any further volunteers. You ran 2.33, but I'm happy to provide
support and coaching for all the documented steps! :-)
--
Cheers,
Carlos.
next prev parent reply other threads:[~2023-03-23 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 15:30 Carlos O'Donell
2023-03-02 16:49 ` Adhemerval Zanella Netto
2023-03-23 13:37 ` Carlos O'Donell [this message]
2023-03-25 19:55 ` Andreas K. Huettel
2023-03-27 14:47 ` Siddhesh Poyarekar
2023-03-27 15:59 ` Andreas K. Huettel
2023-03-27 16:08 ` Siddhesh Poyarekar
2023-03-29 18:35 ` 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=258293c4-1cf4-7825-7de7-5fa56dbf4ff6@redhat.com \
--to=carlos@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=dilfridge@gentoo.org \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=michael.hudson@canonical.com \
--cc=rajis@linux.vnet.ibm.com \
--cc=sam@gentoo.org \
--cc=schwab@suse.de \
--cc=stli@linux.ibm.com \
--cc=szabolcs.nagy@arm.com \
/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).