This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Glibc release check-list
- From: Petr Baudis <pasky at suse dot cz>
- To: libc-alpha at sourceware dot org
- Cc: carlos at systemhalted dot org, ams at gnu dot org
- Date: Fri, 13 Nov 2009 15:28:45 +0100
- Subject: Glibc release check-list
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.)
* 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.)
* Write up an announcement and send it to libc-alpha@ and
libc-announce@. (BTW, no release announcements are sent there for a
while now.)
* Ask Carlos O'Donell <carlos@systemhalted.org> to update the homepage
at gnu.org and sourceware.org.
* Ask Alfred M. Szmidt <ams@gnu.org> to create and upload tarballs on
ftp.gnu.org.
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?
Thanks,
--
Petr "Pasky" Baudis
A lot of people have my books on their bookshelves.
That's the problem, they need to read them. -- Don Knuth