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

Re: svn commit: rev 5960 - branches/release-0.23.0

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-05-19 13:31:10 CEST

On Sat, May 17, 2003 at 11:52:59AM -0400, Michael Price wrote:
> <gentle_reminder>
> No one knows about a change better than the developer who commits the
> change.
> If developers took 30 extra seconds to update the CHANGES file along with
> their
> commit that they already know is going to be user/developer visible then
> errors
> like this would be found a lot sooner. But historically its always been
> easier
> to complain than to actually write half of a line of text :)
> </gentle_reminder>


While true, I worry that updates to the CHANGES file will be inconsistent.
You'll end up with *some* developers tweaking it, and others not. Then the
RM will still need to review the commit list to determine what should go
into the CHANGES file, so there isn't much work saved.

The other problem that I see is simply consistency. Both in terms of wording
and phrasing, but also with the level of detail. There are a lot of commits
that simply don't need to be mentioned in the CHANGES file. Having a single
person review the commits, set an "is this interesting?" bar, and apply it
makes more sense to me, than a whole variety of committers attempting to
divine whether their particular change will be important at release time.



Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 19 13:29:04 2003

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.