On Friday, 30 January 2009, at 15:41:35 (+0100), Vincent Torri wrote: > cedric just fixed a bug in eet, and he forgot to update the ChangeLog. I > do not criticise, it can happen to everyone, including me (and it did > happen to me). > > But, as we plan to do more releases, the ChangeLog will have to always be > updated when such fixes are done, and i think that we should take the > habit of updating the ChangeLog files with some tools that could help us. > > The gstreamer team uses a tool named 'moap' [1] (written by the previous > release manager of gstreamer, btw). I use it for epdf, edvi, eps and evil, > and it is quite nice regarding ChangeLog updates. > > To use it, go to the toplevel directory of the project, then: > > 1) run: > > moap cl prep > > this step modify the ChangeLog according to the modified files > > 2) Update the ChangeLog to add comments > > 3) run > > moap cl ci > > to commit the changes > > Note that i don't want that everyone use that tool and update always the > ChangeLog files right now. I just want to mention one of the features of > that tool, which can help us a lot when we will have to update the > ChangeLog files in the released EFL. > > Finally, last remark: unfortunately, the order of the changes in the > ChangeLog of eet is the reverse of the one that moap uses (currently, last > cahnges are at the bottom, while moap put them at the top of the > ChangeLog). Maybe we can modify the current ChangeLog and use maop for the > updates
The "mzput" utility that comes with Mezzanine opens an editor pre-populated with date, time, and committer name and userid, aborts commits with empty change entries, and auto-appends messages to the Changelog as well as supplying them to the underlying SCM commit (though there is an option to suppress the append). And it maintains the Changelog in chronological order just like the project standard. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <m...@kainx.org> Linux Server/Cluster Admin, LBL.gov Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "I don't think 'huge machine' is the right phrase to describe a cluster of 486/SX's. Maybe 'cluster-f***ed'..." -- Jacob Wilkins ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
