O/H MenTaLguY έγραψε:
On Fri, 2006-08-04 at 08:47 -0700, Jon Phillips wrote:
When one does a release it is asked for to be included along with the release. This is also true of freshmeat.net.
Ah, yeah.. I wonder whether the release notes might not be more helpful than a traditional ChangeLog-format file in that case though.
I think maybe a better option is to have some script which prints out all the commit logs from our repository on make or on a commit so we have something that details the Changelog that people can see when they download inkscape as a package.
I believe some people generate their ChangeLog entries from the SVN log via scripts already, so that should be quite doable.
Anyway, what motivated this was my recent work as primary integrator for 0.44.1. ChangeLog causes a surprising amount of pain when doing merges, and the truth is also that an awful lot of people simply don't bother to update it anyway. If a unified history is easily available from SVN (it wasn't so much with CVS), is it really worth the trouble to also maintain by hand in the tree?
-mental
As I am writing this, the ChangeLog hasn't been updated for about 50 revisions, in the last 8 days. I believe that the ChangeLog is now considered redundant by the majority of developers.
I think the best option would be to delete it from SVN and use 'svn log -r HEAD:r11000' (where 11000 would be the number of the last release) to generate it for releases. SVN also has an XML output option (--xml), so we can create an XSLT document to transform the output to anything we like (HTML, fancy plain text, etc.) on-the-fly.
- Spyros Blanas