Karl Fogel writes:
> 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.)
OK.
> 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 :-).
OK. Any shortcut to coming up with the entries (other than checking the
commit logs and closed issues)?
> 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 :-).
We'll see how that goes :)
Michael Price Member of the Engineering Staff
Distributed Processing Lab; Lockheed Martin Adv. Tech. Labs
A&E 3W; 1 Federal Street; Camden, NJ 08102
856-338-4021, fax 856-338-4144 email: mprice@atl.lmco.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 19 01:49:00 2003