Shortly after the announcement I got a few emails from interested people, including a few from people who have never done a release before. Signed up fo the rest of the year are: particle (1.6), dukeleto (1.7), bernhard (1.8) and gerd (1.9). After that the schedule is wide open.
I've managed a few releases at this point, and I can say with some confidence that it's really not a hard process at all. Actually, there are several steps that I think would be ripe for automation and could become even easier, if an intrepid releaser were interested in doing so. I won't opine about that too much here, just mentioning it off-hand.
Here are the basic steps for making a release.
- Send out some messages on IRC and on the mailing list for people to update NEWS and PLATFORMS.
- Update NEWS and PLATFORMS yourself, because everybody ignored your messages to the mailing list.
- Update the version number in a variety of files, even though we have computer programs and programming languages capable of incrementing digits.
- Come up with a name that's too clever by half. Don't tell anybody, that would ruin the surprise (Since our release schedule is so regular and predictable, we need to have some surprises!)
Waste 20 minutes of your lifeRun fulltest. I like to spend this time watching TV, chatting on IRC, eating junk food, or looking up funny pictures of cats on the interwebs.
- Make the release. This is the hard part: Type "make release VERSION=a.b.c".
- Unpack the tarball into a new directory. Build it and
waste 20 more minutes of your liferun make fulltest again.
- Upload the tarball to the FTP server
- Send out a bunch of announcement emails telling people that we've made a release even though we could program Google Calendar to do this on the third tuesday of the month, every month, for the next thousand years. Tell everybody it's a big deal regardless of how dependable and boring our release cycle is.
- Rake in the karma on IRC.