[gentoo-project] ChangeLog generation - continued discussions

[Fabian Groffen <grobian@gentoo.org>]

Per [1], the discussion on ChangeLog generation should be continued,
since new ideas arose during the council meeting of 20110809.
In the light of [2] on gentoo-scm ML, and in particular the insight
given by robbat2 in [3], the discussion that was started at 19:23
by jmbsvicetto in [4] can now be considered.

I would like to put the remaining open questions for ChangeLog
generation on the agenda of the next Council meeting, so please discuss,
such that we can vote.

Given the earlier votes of the Council to add all commits to ChangeLogs,
I would like to put an additional issue on the table which I encountered
while implementing fully from CVS generated ChangeLogs for the Prefix
rsync tree.
Currently, the ChangeLog file is listed in the Manifest file.  Since it
is generated (from scratch) on rsync0, the ChangeLog file changes
compared to the one the developer used when performing repoman commit.
This means, the generated ChangeLog breaks the Manifest.  For this
reason, the Prefix rsync0 server replaces the digests for the ChangeLog
file in each Manifest file, and then (re)signs it, to solve 1) the
Manifest listing an incorrect digest for the ChangeLog, and 2) the GPG
signature for the Manifest to be incorrect.
A way around this would obviously be to ignore the ChangeLog file, and
not list it in Manifest.  Eventually, in my opinion it should disappear
from VCS anyway, since it's generated on the fly with the information we
like to be in there (in my current approach this is just everything like
current ChangeLogs do).


[1] http://www.gentoo.org/proj/en/council/meeting-logs/20110809-summary.txt
[2] http://archives.gentoo.org/gentoo-scm/msg_454e231a3ff7b7f847c6c5acbebd2bcf.xml
[3] http://archives.gentoo.org/gentoo-scm/msg_64bd32457fe1a55b6250420f8f3fcd01.xml
[4] http://www.gentoo.org/proj/en/council/meeting-logs/20110809.txt

-- 
Fabian Groffen
Gentoo on a different level