1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA512 |
3 |
|
4 |
On 08/03/2011 06:56 PM, Fabian Groffen wrote: |
5 |
> On 03-08-2011 10:43:10 -0700, Donnie Berkholz wrote: |
6 |
>> On 22:16 Mon 01 Aug , Fabian Groffen wrote: |
7 |
>>> Auto generation of ChangeLogs, implies changes, and also |
8 |
>>> influences how current ChangeLog information is to be handled. |
9 |
>>> What if auto-generation is done, what does it take? |
10 |
>> |
11 |
>> For the purposes of a council meeting, I think we should construct |
12 |
>> a small set of specific proposals to choose from so we don't get |
13 |
>> mired in endless discussions during the meeting. |
14 |
>> |
15 |
>> I'd like to offer a couple of them for us to choose between. |
16 |
>> |
17 |
>> 1. Include all commits, don't retroactively change existing |
18 |
>> ChangeLog messages |
19 |
>> |
20 |
>> 2. Allow commit filtering, don't retroactively change existing |
21 |
>> ChangeLog messages |
22 |
>> |
23 |
>> - Filters to allow: keywording, stabilization, removal of ebuilds. |
24 |
>> Whoever implements the code can decide on the format of said |
25 |
>> filters. |
26 |
>> |
27 |
>> |
28 |
>> Do any council members feel strongly that we should include |
29 |
>> additional options, or is it good enough to just make a choice on |
30 |
>> these two? |
31 |
> |
32 |
> I listed the questions I think are relevant at the bottom of my mail. |
33 |
> I feel you forgot the most important one: should ChangeLogs be |
34 |
> auto-generated at all?. Only if yes, |
35 |
|
36 |
I am a bit confused. I though that the previous council had already |
37 |
approved the automated changelog generation[1] |
38 |
|
39 |
[1]: http://www.gentoo.org/proj/en/council/meeting-logs/20110608-summary.txt |
40 |
|
41 |
|
42 |
- -- |
43 |
Regards, |
44 |
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2 |
45 |
-----BEGIN PGP SIGNATURE----- |
46 |
Version: GnuPG v2.0.17 (GNU/Linux) |
47 |
|
48 |
iQIcBAEBCgAGBQJOOZBvAAoJEPqDWhW0r/LC7o8P/2QQKFm8RX+p0bd2O12UErKY |
49 |
8v93pmjhflATLI7l6HCVjfu8GrLMWDcBq/CTRob/bZG3MjZ0rWKYV2KLHaQBssyD |
50 |
zehdjVxzb6w4NopNs+ChxUgPaeOsJmHP+PzhErWZZYPS4Co4U8hrQ0YVaZsb2XC4 |
51 |
cHgCVCJPSmKdHjFp8GBi6vjIz70hAx731oY8i314jQH0B3VlB0BDzXqdX2pX4jp7 |
52 |
yl3pOhUJTzcU4hJQI3fSiYzsXuD7+rH1B4l62+/qiCQggLSG6NSxlKf8hxI8Go4Z |
53 |
moIG/5lT8LR0jm/CLnnOrPKx3wt6VtK2Ysas0q39ixEn7i7Mi1+zF2iZg9+49E9U |
54 |
K2Dlmsae5y1KGWKXeHbuaYkfrc+n7mGTXH1CSiL3YBjSeUvbL9Yx4htOtU+JkqKl |
55 |
rSsQGyFUC2e1Qz+V/iIsxpChZtzcaNCPsd5JID2A93f+liiW0XBbeWa90DADDBUW |
56 |
c3SStxHc1Kh7wAZvd7nVLYXwQGmV7l3lQ6oL43dNzQ2Sgv31Ry91e1+Ci2iqEnwS |
57 |
hddZU9A6dqmnFG59p7WotPmT668adVH/L1UoHc2D6uq1HLHcBP6omtJWGHvxoJ8c |
58 |
bTM2MTe9L5qQlvv1drwnly9RlQpZC5s9UdmcwnIsRIUn6mRoUC4GW54blXomefcT |
59 |
F0NdrZsiDYI9QYrjk9IE |
60 |
=iKn8 |
61 |
-----END PGP SIGNATURE----- |