Michael Price <mprice@atl.lmco.com> writes:
> > 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)?
Actually, all I do is run 'svn log -rX:HEAD > logfile', where X is one
greater than the last documented revision in the CHANGES file. The
trick is set your mental filter; there's millions of little tiny
changes that happen. You need to be able to read the logfile and pick
out the "big" stuff, and you need to distinguish between changes that
ordinary users would notice or not. The only real rules for the
CHANGES file are
- each item should be one line long
- miscellaneous bugs come in a final paragraph at the end of the list.
You'll see the pattern if you read CHANGES.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 19 03:13:07 2003