Doing away with changelogs

[Henry B. Hotz]

For those of us who don't have subversion access, I think the only  
relevant issue is that the change information be reconstructed in a  
ChangeLog file put in the official distributions.

On Apr 8, 2006, at 9:02 AM, krbdev-request at mit.edu wrote:

> Date: Fri, 07 Apr 2006 16:13:02 -0400
> From: Sam Hartman <hartmans at MIT.EDU>
> Subject: Doing away with changelogs
> To: krbdev at MIT.EDU
> Message-ID: <tsl3bgpp2k1.fsf at cz.mit.edu>
> Content-Type: text/plain; charset=us-ascii
>
>
>
> Folks, as we have been using Subversion and branches more, we've  
> been determining that ChangeLog files are hard to deal with in the  
> following ways:
>
> * It is hard to merge them to/from branches
> * Outside developers tend not to update them
> * They tend to repeat a lot of information in subversion logs.
>
> Ken and I would like to consider the possibility of dropping all the
> ChangeLog files from the trunk.  If we do this we'd need to make sure
> that merges contained enough log information that you know what has
> changed.  In particular, if you merge something onto a branch, you
> would want to include the subversion log of the things you are
> merging.  Similarly if you merge a bunch of development onto the
> trunk, include a possibly edited version of that information in the
> subversion log on the trunk.
>
> I'd like to seek comments on this proposal.
>
> --Sam

------------------------------------------------------------------------ 
----
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz at jpl.nasa.gov, or hbhotz at oxy.edu