RFC: CHANGES proposal.

I would like to open up a discussion on the way the CHANGES file is
handled.

Right now it, uh, isn't.

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?

Michael Price Member of the Engineering Staff
Distributed Processing Lab; Lockheed Martin Adv. Tech. Labs
A&E 3W; 1 Federal Street; Camden, NJ 08102
856-338-4021, fax 856-338-4144 email: mprice@atl.lmco.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 20 23:40:41 2003