"Jostein Chr. Andersen" <jostein@josander.net> writes:
> *The committer of a change updates the CANGES file by placeing
> it as a item on the right place when doing the final commit
> for an issue or task. This is good and bad. The committer must
> have a global vue of what to include in the file. On the other
> hand, it saves work for the RM.
>
> *The RM (or another person who can write to the CHANGES file) adds
> items there when he/she/it :-) have time during the time between
> the releases. This may have issues because the items added first
> may not be important in the big picture when the release time
> comes.
>
> *We (usually the RM) tries to do the CHANGES file ASAP on release
> day (or the evening/day before, depending on time, timezones etc)
> and then announce on the dev list that the file are changed.
> I like this alternative best best because then the committers,
> observers, wannabies and other interested persons can speak up.
>
> Comments? I go for the last alternative.
Why not do #2, and then do a sweep over the whole file right before
release? Then you can move or remove less important items, adjust the
overview, etc, yet people will still have had time to review for
accuracy and general inclusiveness.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 16 18:07:16 2004