[Kolab-devel] Re: What is the policy for the ChangeLog file?

[Richard Bos]

Op dinsdag 6 december 2005 18:30, schreef Bernhard Reiter:
> > Only 1 (file).  That is the good thing about it, 1 file describing
> > (summarizing) all changes.  
>
> One per CVS module, you mean...

Indeed, that is indeed what I mean.

> > Especially which files, variables, functions
> > etc changed.  Well see example referred to above.  With that information
> > it is easy to track what changed in last month.  Do you know what
> > happened between Juli 2004 and november 2005 (if you're not interested at
> > all, than no ChangeLog is needed).
>
> CVS will give me a log and a diff if I use the right commands
> to find out what had happened.

The ChangeLog is distributed and installed in the doc directory.  cvs/svn logs 
and diff aren't.  That is another point of using the ChangeLog file.

> > > The next point of thinking about a changelog policy would be
> > > when we switch to a different version control system
> > > (I guess it will be SVN).
> >
> > It is not dependend on cvs, svn, or bitkeeper, etc.  It is up to the
> > group to decide how to deal with it.  I like the ChangeLog it forces me
> > to look over the changes once more, and it is good for others to quickly
> > see what has changed.
>
> Sure, the group will not just change the way of working,
> so having a time when there is thought about Changelogs in general
> is a good time to change a policy.
> My hope is that with SVN we would not need to keep a Changelog manually
> anymore and just have the repository create one.

I use svn and there is still a ChangeLog needed...  See above, the ChangeLog 
file is distributed, as such it is an easy way for your (paying) customers 
what has changed where precisely...


-- 
Richard Bos
Without a home the journey is endless