| 1 |
Am 15.01.2014 04:11, schrieb Tom Wijsman: |
| 2 |
> On Wed, 8 Jan 2014 19:25:19 +0100 |
| 3 |
> SebastianLuther@×××.de wrote: |
| 4 |
> |
| 5 |
>> From: Sebastian Luther <SebastianLuther@×××.de> |
| 6 |
> |
| 7 |
> Can you fix your git config too? See vapier's feedback on creffet. |
| 8 |
|
| 9 |
I'll take a look. |
| 10 |
|
| 11 |
> |
| 12 |
>> +Bugzilla |
| 13 |
>> +-------- |
| 14 |
> |
| 15 |
> More discussion is needed before we should add this; at least I think |
| 16 |
> it should be brought up during the meeting this Sunday, because we've |
| 17 |
> barely had feedback and at least one suggestion doesn't appear |
| 18 |
> discussed and/or incorporated. |
| 19 |
|
| 20 |
I send the first mail with this wording 8 days ago. Enough time to |
| 21 |
comment on it. I'd prefer to discuss it on the list. |
| 22 |
|
| 23 |
> |
| 24 |
> I've commented on the suggestion by dol-sen which I like the most; |
| 25 |
> especially the assignment part, I think it also contains some other neat |
| 26 |
> additions. |
| 27 |
> |
| 28 |
> Besides that, I'll comment my thoughts on some of the other parts here: |
| 29 |
> |
| 30 |
>> +There always exists a tracker bug, named: |
| 31 |
>> +"[Tracker] sys-apps/portage-<next version>". |
| 32 |
>> + |
| 33 |
>> +This bug is renamed from X.Y.Z to X.Y.Z+1 after a release, until |
| 34 |
>> +it gets closed when Y changes and a new one is opened. |
| 35 |
> |
| 36 |
> While this spares out on tracker bugs, we lose the ability to track |
| 37 |
> which bugs were fixed in which version, |
| 38 |
|
| 39 |
That's not true. Just look at the tracker for 2.2.9. Between the renames |
| 40 |
of the tracker you'll see which bug has been marked as blocking. These |
| 41 |
are the fixed ones. |
| 42 |
|
| 43 |
unless we enforce that all bug |
| 44 |
> numbers get to be listed in the ChangeLog; do we have a policy for that? |
| 45 |
|
| 46 |
The numbers go into the ebuild changelog, but I don't think that's |
| 47 |
written down somewhere (/me looks at dol-sen). |
| 48 |
|
| 49 |
> |
| 50 |
>> +Whenever a commit for a specific bug is made to the git repo, |
| 51 |
>> +the corresponding bug gets changed in the following ways: |
| 52 |
>> +* InVCS is added to Keywords |
| 53 |
>> +* The bug is marked as blocking the tracker for the next version |
| 54 |
>> +* A comment is added saying: This is fixed in git: <url to commit> |
| 55 |
>> +(note that the bug stays open) |
| 56 |
> |
| 57 |
> +1 |
| 58 |
> |
| 59 |
>> +After a release all open bugs blocking the tracker are closed |
| 60 |
>> +with the comment "This is fixed in <version>.". |
| 61 |
> |
| 62 |
> +1 |
| 63 |
> |
| 64 |
>> +For individual open bugs it is encouraged to set UNCONFIRMED, |
| 65 |
>> +CONFIRMED or IN_PROGESS as appropriate. |
| 66 |
> |
| 67 |
> What is "as appropriate"? As I mentioned, this needs more discussion; |
| 68 |
> please keep this the way it was, it makes the tracker bug more useful. |
| 69 |
|
| 70 |
The "way it was" is to not care about them at all. There was no |
| 71 |
agreement on the the other thread if these things should be used or not. |
| 72 |
So I left it vague so everyone could use it, but they are not forced to. |
| 73 |
|
| 74 |
> |
| 75 |
>> +There are a number of bugs named "[TRACKER] *" that collect bugs |
| 76 |
>> +for specific topics. Confirmed bugs should be marked as blocking |
| 77 |
>> +these tracker bugs if appropriate. |
| 78 |
> |
| 79 |
> For clarity, it should be mentioned that this does not mean to block |
| 80 |
> the tracker for the next version; this could be misinterpreted. |
| 81 |
|
| 82 |
Considering that the tracker gets renamed, I'm not sure what you mean here. |
| 83 |
|
| 84 |
> |
| 85 |
>> +It is encouraged to set the alias field for frequently used bugs. |
| 86 |
> |
| 87 |
> Yes, but please set it to something specific enough; I'm tired of |
| 88 |
> searching for a random word and get into one or another old bug. |
| 89 |
> |
| 90 |
Most likely candidates are the trackers. |
Archives