[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: Justin Erenkrantz <jerenkrantz_at_apache.org>
Date: 2003-02-21 16:29:55 CET

--On Thursday, February 20, 2003 5:38 PM -0500 Michael Price
<mprice@atl.lmco.com> wrote:

> I would like to propose the following change in the way we do
> things. When you commit what you know is a user-visible change then
> you also update the CHANGES file with an appropriate comment. After
> all, if you are doing something like adding new command line
> options or changing the layout of config files then there isn't
> much doubt about whether or not its going into the file so it might
> as well go in right away.
> Developer-visible changes are more transitory in nature and have a
> way of disappearing as fast as they arrived so I can see delaying
> those entries until the actual release.
> So what does everyone think?

I'm kind of against the developer who wrote the changes making the
CHANGES entry because I see us do it in httpd and APR and frankly, we
are absolutely atrocious at it. It's really hard for some developers
to figure out what is 'user-visible,' 'developer-visible,' or
neither. No amount of prompting is going to help as you run the risk
of being a pest and getting on someone's blacklist yourself. =)

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

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:31:37 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.