A: 

Excel? :)

I'm assuming for each version you first create a list of features to implement, changes to make, bugs to fix etc. Somewhere the status of these must be tracked so you know what is complete, what has been pushed to a later version and so on, and when it's time to test and ship.

This information in your tracking document pretty much contains everything you need.

Andrew Grant
That the point. My tracking document is Bugzilla! All features and bugs to do for the next version are assigned to specific target milestone. All information i need to create a change log are given. But how can i do this without copying everthing to excel, doing the formatting stuff...
Alexander
+1  A: 

Using a custom tool which logs in a database changes per project, module etc. these changes are then exportable to files using a custom addin for finalbuilder for readme production, or exportable to a webservice which imports them into a local db for the webserver so users can view/search online what's changed per module.

Frans Bouma
Yes, writing a custom tool which connects to the database, groups the bugs by their target milestone and status and writes a change log would be a solution.
Alexander
+1  A: 

i think you can have Bugzilla generate it for you. Use the Advanced Bug Search screen, filter on the milestone / version, on the status and resolution. Then you can export it as CSV format and work on it in Excel

chburd
+1  A: 

There is a sourceforge project called Bugzilla Changelog which generate this log as HTML or Wiki - text.

See: Bugzilla Changelog Project

TomTom
Looks exactly what i am searching for. But this projects is not documented. Absolutely no clue how this works.
Alexander
Usually extensions just need to be un-packed and copied to: BUGZILLA_ROOT/extensions/extension_nameBut I'm not a bugzilla admin, perhaps sombody who has more experience with it can explain it better.
TomTom
Thanks. Works perfect now. I had to modify the script a bit because it didn't support different MySQL sockets.
Alexander