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

[Bernhard Reiter]

Am Dienstag, 6. Dezember 2005 18:16 schrieb Richard Bos:
> Op dinsdag 6 december 2005 16:33, schreef Bernhard Reiter:

> It would be ChangeLog (not changelog neither Changelog) as it refers to the
> ChangeLog file, e.g.:
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/ChangeLog?r
>ev=1.5&content-type=text/vnd.viewcvs-markup
>
> > The question then also is: On how many levels should be keep one.
>
> Only 1 (file).  That is the good thing about it, 1 file describing
> (summarizing) all changes.  

One per CVS module, you 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 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.

Bernhard