Wanted: release volunteer

If you've been looking for a non-coding way to help out with
Subversion, this is your chance.

Starting with upcoming release 0.18, we'd like to have a separate
release manager. Until now, one of the Chicago gang has been doing it
(Ben, Mike, or me), but that's not ideal. Releasing can take a few
hours, or sometimes more if problems are discovered. That's at least
a few hours of development time lost, yet there's no reason the
release can't happen in parallel with continuing development. Also,
it's good to have someone who's just worrying about the release, and
not distracted with incoming issues and other stuff.

The process will work something like this:

   1. The milestone is "reached" in a specific revision of trunk,
      except for the administrative work of the release itself.

   2. Then the release manager makes a branch based on that revision.

   3. The release manager brings the CHANGES file up to date.
      (Meanwhile, development continues unabated on trunk.)

   4. Release manager bumps the version number on the branch, rolls a
      tarball based on the branch, tests it, uploads it, announces,
      etc, as documented in notes/tarball_release_procedure.txt (oh,
      we should change that document to reflect the new process, I
      suppose).

   5. After release, the release manager ports the release-specific
      changes over to trunk.

We'll set you up with the necessary commit access to edit the CHANGES
file, create the branch, etc; and we'll be available on the list to
help, of course.

Please follow up to the list if you'd like to volunteer!

Thanks,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 14 22:51:46 2003