get rid of ChangeLog?
Would anyone object if I got rid of the ChangeLog? It's not getting updated enough, it's redundant with respect to the svn log and the release notes, and it's being a royal pain when trying to merge stuff from trunk.
-mental
On 8/2/06, MenTaLguY <mental@...3...> wrote:
Would anyone object if I got rid of the ChangeLog? It's not getting updated enough, it's redundant with respect to the svn log and the release notes, and it's being a royal pain when trying to merge stuff from trunk.
I certainly would welcome this.
On Wed, 2006-08-02 at 20:21 -0400, MenTaLguY wrote:
Would anyone object if I got rid of the ChangeLog? It's not getting updated enough, it's redundant with respect to the svn log and the release notes, and it's being a royal pain when trying to merge stuff from trunk.
I dunno...its an important document for many people and systems (like sf.net).
I think best approach would be to put a link in it to where we do maintain logs for a release, or to the release notes.
Jon
-mental
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=D... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Thu, 2006-08-03 at 12:11 -0400, MenTaLguY wrote:
On Wed, 2006-08-02 at 23:20 -0700, Jon Phillips wrote:
I dunno...its an important document for many people and systems (like sf.net).
Hmm, how does SourceForge use it?
-mental
When one does a release it is asked for to be included along with the release. This is also true of freshmeat.net.
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.
Also, we could, as a matter of policy just tell people to only commit messages to SVN commits.
Another thought is that this script could just take the form of a Make directive so we can get: make Changelog
That way we can include the standard Changelog with our releases and make both parties happy and reduce duplication of efforts.
Jon
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=D... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
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
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
participants (4)
-
bulia byak -
Jon Phillips -
MenTaLguY -
Spyros Blanas