public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev] ChangeLog generation - pros and cons (council discussion request)
Date: Wed, 03 Aug 2011 19:16:15 +0100	[thread overview]
Message-ID: <4E39906F.8070300@gentoo.org> (raw)
In-Reply-To: <20110803175650.GN20656@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 08/03/2011 06:56 PM, Fabian Groffen wrote:
> On 03-08-2011 10:43:10 -0700, Donnie Berkholz wrote:
>> On 22:16 Mon 01 Aug     , Fabian Groffen wrote:
>>> Auto generation of ChangeLogs, implies changes, and also
>>> influences how current ChangeLog information is to be handled.
>>> What if auto-generation is done, what does it take?
>> 
>> For the purposes of a council meeting, I think we should construct
>> a small set of specific proposals to choose from so we don't get
>> mired in endless discussions during the meeting.
>> 
>> I'd like to offer a couple of them for us to choose between.
>> 
>> 1. Include all commits, don't retroactively change existing
>> ChangeLog messages
>> 
>> 2. Allow commit filtering, don't retroactively change existing
>> ChangeLog messages
>> 
>> - Filters to allow: keywording, stabilization, removal of ebuilds.
>>  Whoever implements the code can decide on the format of said
>> filters.
>> 
>> 
>> Do any council members feel strongly that we should include
>> additional options, or is it good enough to just make a choice on
>> these two?
> 
> I listed the questions I think are relevant at the bottom of my mail.
> I feel you forgot the most important one: should ChangeLogs be 
> auto-generated at all?.  Only if yes,

I am a bit confused. I though that the previous council had already
approved the automated changelog generation[1]

[1]: http://www.gentoo.org/proj/en/council/meeting-logs/20110608-summary.txt


- -- 
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iQIcBAEBCgAGBQJOOZBvAAoJEPqDWhW0r/LC7o8P/2QQKFm8RX+p0bd2O12UErKY
8v93pmjhflATLI7l6HCVjfu8GrLMWDcBq/CTRob/bZG3MjZ0rWKYV2KLHaQBssyD
zehdjVxzb6w4NopNs+ChxUgPaeOsJmHP+PzhErWZZYPS4Co4U8hrQ0YVaZsb2XC4
cHgCVCJPSmKdHjFp8GBi6vjIz70hAx731oY8i314jQH0B3VlB0BDzXqdX2pX4jp7
yl3pOhUJTzcU4hJQI3fSiYzsXuD7+rH1B4l62+/qiCQggLSG6NSxlKf8hxI8Go4Z
moIG/5lT8LR0jm/CLnnOrPKx3wt6VtK2Ysas0q39ixEn7i7Mi1+zF2iZg9+49E9U
K2Dlmsae5y1KGWKXeHbuaYkfrc+n7mGTXH1CSiL3YBjSeUvbL9Yx4htOtU+JkqKl
rSsQGyFUC2e1Qz+V/iIsxpChZtzcaNCPsd5JID2A93f+liiW0XBbeWa90DADDBUW
c3SStxHc1Kh7wAZvd7nVLYXwQGmV7l3lQ6oL43dNzQ2Sgv31Ry91e1+Ci2iqEnwS
hddZU9A6dqmnFG59p7WotPmT668adVH/L1UoHc2D6uq1HLHcBP6omtJWGHvxoJ8c
bTM2MTe9L5qQlvv1drwnly9RlQpZC5s9UdmcwnIsRIUn6mRoUC4GW54blXomefcT
F0NdrZsiDYI9QYrjk9IE
=iKn8
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2011-08-03 18:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110602091338.GL14065@gentoo.org>
2011-08-01 20:16 ` [gentoo-project] Re: [gentoo-dev] ChangeLog generation - pros and cons (council discussion request) Fabian Groffen
2011-08-03 17:43   ` Donnie Berkholz
2011-08-03 17:56     ` Fabian Groffen
2011-08-03 18:09       ` Donnie Berkholz
2011-08-03 18:33         ` Fabian Groffen
2011-08-09 17:32           ` Donnie Berkholz
2011-08-09 17:42             ` Fabian Groffen
2011-08-09 18:15               ` Donnie Berkholz
2011-08-09 18:22                 ` Fabian Groffen
2011-08-09 20:20                   ` Donnie Berkholz
2011-08-09 20:26                     ` Fabian Groffen
2011-08-09 18:34                 ` Samuli Suominen
2011-08-03 18:16       ` Markos Chandras [this message]
2011-08-03 18:30         ` Fabian Groffen
2011-08-03 18:39           ` Markos Chandras
2011-08-03 18:43             ` Fabian Groffen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E39906F.8070300@gentoo.org \
    --to=hwoarang@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox