-----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-----