Karl Fogel writes:
> 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.
>
> [snip]
>
> 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).
Could you elaborate on "tests it"? I can easily run the ra_local and
ra_svn tests on multiple platforms and an ra_dav test on one. However,
they would all be Unix boxes as I have no access to a Windows box (and
am very happy as a result :)
> 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!
Depends on your answer to the question above. I'm certainly
"interested".
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 14 23:16:12 2003