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

Re: RFC: CHANGES proposal.

From: <cmpilato_at_collab.net>
Date: 2003-02-21 14:46:08 CET

Justin Erenkrantz <jerenkrantz@apache.org> writes:

> I'd rather the CHANGES file not end up like the unreadable and
> unintelligable cruft that we have in httpd. I like Subversion's
> succint and readable CHANGES file.
>
> But, that's just me. -- justin

Me, too. I find, for example, that Ben does a great job of keeping
the changes concise enough to fit on a line, yet detailed enough to
make sense. There is a certain amount of skill present there, and I
foresee time wasted when those who do not possess that skill have
their CHANGES mods corrected by those who do.

Also, the one time I've actually done the CHANGES updates for a
release (or at least part of them), I was thrilled by how much of a
"big picture" understanding of that release I was able to gain. A
release manager is effectively taking responsibility for an entire set
of changes being tossed into the general public. I think an RM should
have that "big picture" understanding of what he or she is claiming as
good, and the CHANGES updates pretty much force that to happen.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 21 16:47:52 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.