16 Dec
2010
16 Dec
'10
6:02 p.m.
#224: Automatically generate ChangeLog entries
--------------------------+-------------------------------------------------
Reporter: levill_r | Owner: levill_r
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Milena | Version: 1.0
Resolution: | Keywords:
--------------------------+-------------------------------------------------
Old description:
Instead of documenting changes both in Git messages
''and'' !ChangeLog
entries, just rely on the first and generate the latter.
Use Jim Meyering's `git-to-changelog` script.
* http://git.savannah.gnu.org/cgit/gnulib.git/plain/build-aux/gitlog-to-
changelog
We can pick some hints and ideas here:
* http://git.savannah.gnu.org/cgit/coreutils.git/plain/HACKING
* http://git.savannah.gnu.org/cgit/coreutils.git/plain/Makefile.am
* http://cyberelk.net/tim/2009/06/25/generating-changelog-files-from-
commit-logs/
I suggest we still
1. Record the !ChangeLog into the repository, so that we can fix it (and
keep the fixes!).
1. Keep the date of the last !ChangeLog generation so that we generate
only the missing entries next time.
There's a additional problem with Olena's repository: we have several
!ChangeLogs and the system should be either smart enough to find the
right !ChangeLog (!ChangeLogs?) or accept tags/metadata to generate
entries at the right place.
New description:
Instead of documenting changes both in Git messages ''and'' !ChangeLog
entries, just rely on the first and generate the latter.
Use Jim Meyering's `git-to-changelog` script.
* http://git.savannah.gnu.org/cgit/gnulib.git/plain/build-aux/gitlog-to-
changelog
We can pick some hints and ideas here:
* http://git.savannah.gnu.org/cgit/coreutils.git/plain/HACKING
* http://git.savannah.gnu.org/cgit/coreutils.git/plain/Makefile.am
* http://cyberelk.net/tim/2009/06/25/generating-changelog-files-from-
commit-logs/
I suggest we still
1. Record the !ChangeLog into the repository, so that we can fix it (and
keep the fixes!).
1. Keep the date of the last !ChangeLog generation so that we generate
only the missing entries next time.
See how we handled this issue in TC (target `update-ChangeLog`).
There's an additional problem with Olena's repository: we have several
!ChangeLogs and the system should be either smart enough to find the right
!ChangeLog (!ChangeLogs?) or accept tags/metadata to generate entries at
the right place.
--
Comment(by levill_r):
Mention TC.
--
Ticket URL: <https://trac.lrde.org/olena/ticket/224#comment:2>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient C++ image processing library.