I'm summarising this thread [0] for the upcoming council meeting.
Automatic ChangeLog generation
Some people have expressed disagreement with committing ChangeLog
updates for some changes. Discussion on that lead to an updated policy
to document nearly all changes. Some people still really
On 09-06-2011 18:06:02 +0200, Andreas K. Huettel wrote:
If typos matter then they matter to everybody, and if they don't then
we should not care. QA in Gentoo should be a consistent experience.
while the last sentence is true, the first is not. if a minority of
people care about
On Tue, Jun 7, 2011 at 17:20, Mike Frysinger wrote:
On Thursday, June 02, 2011 05:13:38 Fabian Groffen wrote:
- inability to edit ChangeLog entries (typos, bug refs, etc.)
in practice, i rarely see this being an issue. it certainly hasnt impeded any
of the huge projects out there (many of
On Thu, Jun 9, 2011 at 1:59 AM, Mike Frysinger vap...@gentoo.org wrote:
thinking about it a little more, i think this can easily be addressed.
only auto-generate the ChangeLog file if it doesnt exist in VCS.
thus the few people who are actually anal about typos (or just think
they are) can
On Thu, Jun 9, 2011 at 07:14, Rich Freeman wrote:
On Thu, Jun 9, 2011 at 1:59 AM, Mike Frysinger wrote:
thinking about it a little more, i think this can easily be addressed.
only auto-generate the ChangeLog file if it doesnt exist in VCS.
thus the few people who are actually anal about typos
Mike,
If typos matter then they matter to everybody, and if they don't then
we should not care. QA in Gentoo should be a consistent experience.
while the last sentence is true, the first is not. if a minority of
people care about typos, and/or they rarely fix said typos, then the
On Thursday, June 09, 2011 12:06:02 Andreas K. Huettel wrote:
If typos matter then they matter to everybody, and if they don't then
we should not care. QA in Gentoo should be a consistent experience.
while the last sentence is true, the first is not. if a minority of
people care
On Thu, 9 Jun 2011 12:40:46 -0400
Mike Frysinger vap...@gentoo.org wrote:
what exactly is your point ? nowhere did i say i wasnt going to
follow the new policy in this case. this e-mail is, as you said
yourself, a waste of time.
Instead, you said you'd just not properly maintain packages, by
On Thursday, June 09, 2011 12:47:02 Ciaran McCreesh wrote:
On Thu, 9 Jun 2011 12:40:46 -0400 Mike Frysinger wrote:
what exactly is your point ? nowhere did i say i wasnt going to
follow the new policy in this case. this e-mail is, as you said
yourself, a waste of time.
Instead, you
the contact forms located there to send us your
question.
Original Message Follows:
From: Mike Frysinger vap...@gentoo.org
Subject: [gentoo-dev] ChangeLog generation - pros and cons (council
discussion request)
Date: Thu, 9 Jun 2011 16:01:42 -0400
On Thursday, June 09
On Thursday, June 02, 2011 05:13:38 Fabian Groffen wrote:
Simple pros I see mentioned:
additional pro: automatic culling of information no longer relevant. entries
dating back to 2002 rarely are useful today. we could easily implement a cap
via date, size, files still in the tree, # of
On 02-06-2011 17:15:11 +0530, Nirbheek Chauhan wrote:
All these problems are fixed if we don't re-generate the *existing*
ChangeLogs. We should simply archive the existing ChangeLog, and
append to it after the move to git.
About this slightly hybrid approach:
- the ChangeLog file is retained,
On Sun, Jun 5, 2011 at 1:30 PM, Fabian Groffen grob...@gentoo.org wrote:
On 02-06-2011 17:15:11 +0530, Nirbheek Chauhan wrote:
All these problems are fixed if we don't re-generate the *existing*
ChangeLogs. We should simply archive the existing ChangeLog, and
append to it after the move to
On Thu, Jun 2, 2011 at 2:43 PM, Fabian Groffen grob...@gentoo.org wrote:
I start from the assumption that generation of ChangeLogs is NOT limited
to any VCS.
This assumption is incorrect, but I guess it's a close enough
approximation for the current discussion.
Simple pros I see mentioned:
-
On 02-06-2011 17:15:11 +0530, Nirbheek Chauhan wrote:
- no discussion on what to include or not (everything is in there)
In git, we can make git log skip commit messages while generating the
ChangeLog, so this is incorrect. See section Commit Limiting in git
log --help.
Assuming this is
On Thu, Jun 2, 2011 at 6:29 PM, Fabian Groffen grob...@gentoo.org wrote:
On 02-06-2011 17:15:11 +0530, Nirbheek Chauhan wrote:
- no discussion on what to include or not (everything is in there)
In git, we can make git log skip commit messages while generating the
ChangeLog, so this is
16 matches
Mail list logo
