kfogel@collab.net writes:
> * Update the CHANGES file. This basically means going over all the
> commits since the last release, and summarizing them in a way
> that tells users and developers the important news, but doesn't
> overwhelm them in details. In order to do this, one must
> (obviously) be able to distinguish branch changes from trunk
> changes, tell what's been merged, and understand the user-visible
> implications of each change.
Karl's right; this really is the hardest job. It needs to be done by
someone who is *actively* reading the dev-list discussions, watching
the commits happen every day, and understand how these activities
relateto each other. So when it comes time to reading all the commit
log messages, you say, "ah yes, I understand what this commit is
about, and I remember people talking about it, and I think it merits
its own line in the CHANGES file."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 27 04:28:37 2003