Re: [GD-DEVEL] New commits

Pierre writes:
> Hell Lars,
> 
> I saw your first commits this morning, welcome on board!
 
 Thanks :)

> I added all files of all past GD releases. One of them has a ChangeLog
> file. But it was not really a ChangeLog.
>  
> To ease my work, I created a "ISSUES" file. Each change has an id
> which will match the issue Id in the tracker. Can you add your changes
> in there? If it is related to one entry, like fixing a fix, there is
> no need to create a new one.
> 
> It is not used directly now, but the format of the commit msg should be:
> #123, description of the commit
> 
> where 123 is the issue id. Once the issues tracker is online, it will
> provide patches for each issue using all relevant commits. The final
> goal is to get the release changelog generated by the tracker.

 ISSUES, to me, sounds a lot like "known bugs", although from the actual
 contents it's clear they're fixes.

 I pretty much prefer a detailed ChangeLog file. Together with "cvs history"
 (which seems broken here, incidentally:

$ cvs history gdtest.c
cvs history: warning: history line 1 invalid
O 2006-10-11 09:40 +0000 lhecking gd =gd= <remote>/*
$ 

 ), it provides an excellent audit trail. Tracker #s can and should be
 referenced. Here's an example how we do it in gnuplot:

| 2006-10-03  Hans-Bernhard Broeker  <[email protected]>
|  
|         * src/graph3d.c (place_arrows3d): Clip arrows even in 3D.  Patch
|         from Harald Harders (SF #1569232).

 But I'll go with what is there right now. I don't want to start a holy
 war just yet ;-)

> By the way, if you like to remove the "configure" and related data
> from cvs and add an autogen.sh, please do, we have to do it anyway :)
 
 Will do, but it might take a day or two.