Re: New release manager needed.

pll@lanminds.com writes:

> In release.txt it says:
>
> 1. Tweak trunk/CHANGES to contain all the latest changes
>
> How do I know what all the latest changes are? Is that stuff I
> need to gather from an svn diff of the last release or comb through
> the mail archives, etc.?

Look and see at what point the last release branch was copied from
trunk. Assume it branched off of /trunk in revision 6000. Then you
would run

   'svn log -v -r6000:HEAD > logfile'

Then you read 'logfile' very carefully, and try to write a consise
summary of important events.

> Just curious about what I'm supposed to be putting in there.

This is the toughest "human" part of being a release manager. The
CHANGES file has a very specific, very terse format. It does not list
every single change. It only lists the "most important" ones, which
is a subjective call. How do you make the subjective call? Read
through the earlier CHANGES entries and try to get a feel for the
"filter" that people were using, and then try to preserve that filter
when you start reading commit-logs yourself. It's not an easy thing
to do. :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 2 19:26:41 2003