[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

CHANGES - Misc. stuff

From: Jostein Chr. Andersen <jostein_at_josander.net>
Date: 2004-01-16 17:34:03 CET


The thread on the devlist starting with this posting..
..begs for more time from the CHANGES file are visible in trunk until its
content are frozen (when copied to the release branch).
That message camed up because a important change in the Perl bindings did
not appear in the file (from #svn last Tuesday)

People have various opinions of the contents of this file so I have some
suggestions/alternatives on how to avoid this in the future:

*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

*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.


http://www.josander.net/kontakt/ ||
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 16 17:36:27 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.