Ben's still cleaning up some bits for issue #724 (we got a little
sidetracked w/ the revision 4943 stuff). When Ben closes 724, that's
the signal to start the release process. (If #639 is done for 0.18,
great, if not, it won't kill us to carry it over into the next
milestone.)
I'd say start writing the CHANGES entry for 0.18 now, though, since we
already know all the changes. Commit that on trunk, then branch from
there and do the rest the release from the branch. Ben has done the
CHANGES summaries in the past, so he can answer any questions about
the extra-terse style of that file :-).
Oh, also, bump subversion/include/svn_version.h on the trunk before
branching -- otherwise we could have people reporting bugs from
bleeding edge dev builds that "look older than" release builds. Even
if the branch needs tweaks after releasing, it's okay for the trunk to
reflect the new version number already.
If you find that other release apparatus (such as dist.sh) has
deficiencies that need correcting, then let us know and we'll get it
fixed. In part this first volunteer-managed release is about making
the whole process easier for next time, I think :-).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 19 00:53:58 2003