This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Glibc release check-list
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: Petr Baudis <pasky at suse dot cz>
- Cc: libc-alpha at sourceware dot org, ams at gnu dot org
- Date: Fri, 13 Nov 2009 10:00:10 -0500
- Subject: Re: Glibc release check-list
- References: <20091113142845.GS3708@machine.or.cz>
On Fri, Nov 13, 2009 at 9:28 AM, Petr Baudis <pasky@suse.cz> wrote:
> ?Hi!
>
> ?What all is needed to officially release a revision of a stable
> branch, e.g. 2.10.2 or 2.11.1? (After discussion, I will of course put
> this on the wiki.)
Just to clarify, I think the order should be:
> ?* Create tag glibc-2.M.N and push it out. (Or do we want to use
> release/2.M/2.M.N for tags as well? It seems a bit clumsy and tag for
> stable releases would be hard to find for glibc newbies, IMHO.)
1st.
> ?* Write up an announcement and send it to libc-alpha@ and
> libc-announce@. (BTW, no release announcements are sent there for a
> while now.)
4th.
> ?* Ask Carlos O'Donell <carlos@systemhalted.org> to update the homepage
> at gnu.org and sourceware.org.
3rd.
> ?* Ask Alfred M. Szmidt <ams@gnu.org> to create and upload tarballs on
> ftp.gnu.org.
2nd.
> ?I'm the least sure about the last point - signing of the tarballs is
> also involved; will Alfred take care of all that, or should Roland be
> signing all releases, or should the release manager be involved in this?
>
> ?Is this all?
For glibc proper? Yes, I think so.
The ports repository still needs tagging/branching, but that can come
a little later.
Cheers,
Carlos.