KDE 4.1 Changelog?

[Robert Knight]

Hello,

Apologies if I am treading on ground which has already been discussed
in-depth here:

Updating a single XML changelog which is kept in a completely different
part of the tree from which individual developers normally work is an
awkward process.  I think this explains why it rarely seems complete.  

gnomies keep a simple text based ChangeLog file in the root of each
project and then run a script to build the final log (in whatever
format).  That would probably get better results.  Plus it would be
easier to automatically ping the right developers to provide an
up-to-date log.

I presume there are reasons why an XML file was chosen, can anyone
enlighten me?


> when we commit bugfixes
> > since they will not be reflected in a 4.0.6 changelog

Do we not have any tools to do this automatically from the "BUG: XYZ" commit messages?

> We do 
> have the goals page that should give an overview at a reasonable level.

That has the same problem really.  It is disconnected from the other heavily
used tools (bugs.kde.org, files in whatever part of the tree).    

Regards,
Robert.

On Tue, 2008-06-03 at 12:40 +0200, Sebastian Kügler wrote:
> On Tuesday 03 June 2008 04:52:37 Michael Pyne wrote:
> > Are we using the Changelog XML[1] for the 4.1 changelog or the Feature
> > Plan?  The reason I'm asking is that the XML changelog is rather sparse and
> > with the last release of 4.0.5 coming up (not to mention 4.1) we need to
> > start looking towards updating the 4.1 changelog when we commit bugfixes
> > since they will not be reflected in a 4.0.6 changelog. If we're using a
> > different changelog just let me know so I can update appropriately please.
> > [1] trunk/www/sites/www/announcements/changelogs/changelog_branch_4_1.xml
> 
> For 4.0 -> 4.1, getting the XML changelog filled sounds ... unrealistic. We do 
> have the goals page that should give an overview at a reasonable level. For 
> the x.y.z releases, let's continue to use the changelogs in XML.