| 1 |
On Wed, 8 Jan 2014 19:25:19 +0100 |
| 2 |
SebastianLuther@×××.de wrote: |
| 3 |
|
| 4 |
> From: Sebastian Luther <SebastianLuther@×××.de> |
| 5 |
|
| 6 |
Can you fix your git config too? See vapier's feedback on creffet. |
| 7 |
|
| 8 |
> +Bugzilla |
| 9 |
> +-------- |
| 10 |
|
| 11 |
More discussion is needed before we should add this; at least I think |
| 12 |
it should be brought up during the meeting this Sunday, because we've |
| 13 |
barely had feedback and at least one suggestion doesn't appear |
| 14 |
discussed and/or incorporated. |
| 15 |
|
| 16 |
I've commented on the suggestion by dol-sen which I like the most; |
| 17 |
especially the assignment part, I think it also contains some other neat |
| 18 |
additions. |
| 19 |
|
| 20 |
Besides that, I'll comment my thoughts on some of the other parts here: |
| 21 |
|
| 22 |
> +There always exists a tracker bug, named: |
| 23 |
> +"[Tracker] sys-apps/portage-<next version>". |
| 24 |
> + |
| 25 |
> +This bug is renamed from X.Y.Z to X.Y.Z+1 after a release, until |
| 26 |
> +it gets closed when Y changes and a new one is opened. |
| 27 |
|
| 28 |
While this spares out on tracker bugs, we lose the ability to track |
| 29 |
which bugs were fixed in which version, unless we enforce that all bug |
| 30 |
numbers get to be listed in the ChangeLog; do we have a policy for that? |
| 31 |
|
| 32 |
> +Whenever a commit for a specific bug is made to the git repo, |
| 33 |
> +the corresponding bug gets changed in the following ways: |
| 34 |
> +* InVCS is added to Keywords |
| 35 |
> +* The bug is marked as blocking the tracker for the next version |
| 36 |
> +* A comment is added saying: This is fixed in git: <url to commit> |
| 37 |
> +(note that the bug stays open) |
| 38 |
|
| 39 |
+1 |
| 40 |
|
| 41 |
> +After a release all open bugs blocking the tracker are closed |
| 42 |
> +with the comment "This is fixed in <version>.". |
| 43 |
|
| 44 |
+1 |
| 45 |
|
| 46 |
> +For individual open bugs it is encouraged to set UNCONFIRMED, |
| 47 |
> +CONFIRMED or IN_PROGESS as appropriate. |
| 48 |
|
| 49 |
What is "as appropriate"? As I mentioned, this needs more discussion; |
| 50 |
please keep this the way it was, it makes the tracker bug more useful. |
| 51 |
|
| 52 |
> +There are a number of bugs named "[TRACKER] *" that collect bugs |
| 53 |
> +for specific topics. Confirmed bugs should be marked as blocking |
| 54 |
> +these tracker bugs if appropriate. |
| 55 |
|
| 56 |
For clarity, it should be mentioned that this does not mean to block |
| 57 |
the tracker for the next version; this could be misinterpreted. |
| 58 |
|
| 59 |
> +It is encouraged to set the alias field for frequently used bugs. |
| 60 |
|
| 61 |
Yes, but please set it to something specific enough; I'm tired of |
| 62 |
searching for a random word and get into one or another old bug. |
| 63 |
|
| 64 |
-- |
| 65 |
With kind regards, |
| 66 |
|
| 67 |
Tom Wijsman (TomWij) |
| 68 |
Gentoo Developer |
| 69 |
|
| 70 |
E-mail address : TomWij@g.o |
| 71 |
GPG Public Key : 6D34E57D |
| 72 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives