1 |
I'm summarising this thread [0] for the upcoming council meeting. |
2 |
|
3 |
|
4 |
Automatic ChangeLog generation |
5 |
|
6 |
Some people have expressed disagreement with committing ChangeLog |
7 |
updates for some changes. Discussion on that lead to an updated policy |
8 |
to document nearly all changes. Some people still really disagree with |
9 |
that and go as far to commit dummy placeholders just to make sure they |
10 |
don't do what they deem is useless for everybody. |
11 |
|
12 |
ChangeLog generation is often suggested as a solution to this by those |
13 |
people who do not like to document their changes in the ChangeLog file. |
14 |
|
15 |
Auto generation of ChangeLogs, implies changes, and also influences how |
16 |
current ChangeLog information is to be handled. |
17 |
What if auto-generation is done, what does it take? |
18 |
|
19 |
- what messages to include (all?), what not to include (ignore some?) |
20 |
-- ignore some messages, git: Commit Limiting ([trivial]) [1][3] |
21 |
--- policy? what to ignore, what not? what does the current policy mean |
22 |
if commits can be made to be ignored? |
23 |
-- only include messages for a time range, or relevant messages for |
24 |
current files (ebuilds) in the directory (package) [3] |
25 |
|
26 |
= balance between hard policy effectuated by the generation and fuzzy |
27 |
control via keywords that is subject to the interpretation of the |
28 |
committer |
29 |
= opening for new opportunities to safe space for and present more |
30 |
relevant information to our users |
31 |
|
32 |
- inability to edit changelog entries (make corrections) |
33 |
-- git: git notes --help -> append notes to commit msgs [1] |
34 |
-- not a real issue [3] |
35 |
|
36 |
= balance between either allowing it through complex scripting, or just |
37 |
ignoring the ability at all since it is rarely used and not done by |
38 |
others either ([3]) |
39 |
|
40 |
- history, ChangeLogs are often more useful than the CVS logs |
41 |
-- retain existing ChangeLog and append? [1] |
42 |
--- use setup with separate git repo for ChangeLogs [2] |
43 |
--- auto-generate if non-existent (per maintainer pref) [3] |
44 |
-- just forget it, it's old [3] |
45 |
|
46 |
= balance between either retaining the original information, or |
47 |
forgetting about it completely since it is likely outdated information |
48 |
anyway -- note: this is only about differences in CVS log and |
49 |
ChangeLog |
50 |
= balance between generating all ChangeLogs, or just those whose |
51 |
maintainer likes it |
52 |
|
53 |
|
54 |
Generating ChangeLog opens opportunities (only commit, limit contents, |
55 |
consistency), and can ease the life of developers. However, the |
56 |
currently existing ChangeLog files might differ from a generated one |
57 |
from VCS logs significantly, if this is considered important, a strategy |
58 |
for retaining the old messages has to be deployed (keep ChangeLog file, |
59 |
store ChangeLog in separate repo, selectively retain ChangeLog files per |
60 |
package). |
61 |
|
62 |
If a ChangeLog is generated, are all commits to show up in them, or can |
63 |
certain messages be ignored? The latter requires specification of how, |
64 |
but also when. Updating a ChangeLog file is close to such situation |
65 |
without policies. Since commit messages cannot be changed, are methods |
66 |
necessary to add notices to messages when they appear wrong/incorrect? |
67 |
|
68 |
Should ChangeLogs be generated? |
69 |
If yes |
70 |
- should all commit message be included |
71 |
- should commit messages be appended to/updated? |
72 |
- should existing information in ChangeLog files be retained? |
73 |
|
74 |
|
75 |
[0] http://archives.gentoo.org/gentoo-dev/msg_2ff02d6910d797045af3659fb21c712f.xml |
76 |
[1] http://archives.gentoo.org/gentoo-dev/msg_934d783d619540a2e97725da7e767253.xml |
77 |
[2] (not on archives.g.o and gmane) http://www.gossamer-threads.com/lists/gentoo/dev/231903?do=post_view_threaded |
78 |
[3] http://archives.gentoo.org/gentoo-dev/msg_3156112af9944a6c8736159247275ccb.xml |
79 |
|
80 |
|
81 |
|
82 |
On 02-06-2011 11:13:38 +0200, Fabian Groffen wrote: |
83 |
> Following up on the recent discussions about ChangeLogs, and what should |
84 |
> be in there, versus what not, this email tries to describe the pros and |
85 |
> cons of the frequently mentioned generation of ChangeLogs from the VCS |
86 |
> we use. |
87 |
> |
88 |
> I would like the council to discuss the generation of ChangeLogs from |
89 |
> the VCS in the next meeting for which this message is in time. I prefer |
90 |
> the council to decide upon whether or not generation of ChangeLogs is |
91 |
> desirable for Gentoo or not. In this email, I will try to describe the |
92 |
> pros and cons, but I invite anyone else to contribute/discuss ideas. |
93 |
|
94 |
|
95 |
-- |
96 |
Fabian Groffen |
97 |
Gentoo on a different level |