Gentoo Archives: gentoo-dev

From: Ioannis Aslanidis <aslanidis@×××××.com>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Suggestion: INVALID -> NOCHANGE in bugzilla
Date: Sat, 24 Mar 2007 21:07:00
Message-Id: 460591F8.6010409@gmail.com
In Reply to: Re: [gentoo-dev] Suggestion: INVALID -> NOCHANGE in bugzilla by "Kevin F. Quinn"
1 I think that there is a problem of concept. If a bug is marked INVALID,
2 it's because it is not a real bug. Marking a bug NOCHANGE or
3 NOCHANGEREQUIRED, not only overlaps with other resolutions, but fails to
4 better explain the reason why the bug was closed, whereas INVALID indeed
5 means that the reported bug is simply not a bug or that it was reported
6 to the wrong place.
7
8 Even though it might look harsh to the user to get such a resolution,
9 it's also harsh for the developers to have to handle bugs that are not
10 related to them.
11
12 Still, changing the name from INVALID to NOTABUG + NOTOURBUG does make
13 sense, as the meaning doesn't get lost.
14
15 Kevin F. Quinn wrote:
16 > On Sat, 24 Mar 2007 19:14:38 +0100
17 > Marius Mauch <genone@g.o> wrote:
18 >
19 >> On Sat, 24 Mar 2007 18:34:21 +0100
20 >> "Kevin F. Quinn" <kevquinn@g.o> wrote:
21 >>
22 >>> People reporting bugs often get annoyed when their bug is marked
23 >>> INVALID; especially when they're relatively new to the Gentoo
24 >>> Experience. We've all seen it many times, I'm sure.
25 >>>
26 >>> Arguably no bug is invalid in the normal sense - if someone raises
27 >>> an issue, they have an issue, regardless what we think of it. To
28 >>> that end I'd like to propose bugzilla be reconfigured to use the
29 >>> phrase "NOCHANGE" instead of "INVALID". NOCHANGE would indicate
30 >>> that whatever the original issue, no change is needed on our part to
31 >>> resolve the issue.
32 >> _If_ it's changed then please to something else, NOCHANGE would
33 >> overlap with other values (WONTFIX, CANTFIX, WORKSFORME) and isn't
34 >> that obvious to me at least. A fake resolution that's mentioned on
35 >> IRC from time to time is NOTABUG which would fit better here.
36 >
37 > Well, I meant for NOCHANGE to be "no change needed", but figured
38 > NOCHANGEREQUIRED is a bit longwinded. It implies the issue is
39 > understood, it has been explained to the bug reporter, but requires no
40 > change to anything:
41 >
42 > CANTFIX: the problem exists, but no sensible way to fix it exists
43 > WONTFIX: the problem exists, but for some reason it won't be fixed
44 > WORKSFORME: can't replicate
45 >
46 > NOCHANGE: no change needed
47 >
48 > The problem I have with NOTABUG is pretty much the same problem I have
49 > with INVALID - it's not as severe, but it still does the same thing to
50 > the user (i.e. slaps him with a wet fish rather than a frozen one).
51 >
52 --
53 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] Suggestion: INVALID -> NOCHANGE in bugzilla "Kevin F. Quinn" <kevquinn@g.o>