1 |
Well, I personally would prefer to have two keywords at least, one for |
2 |
candidates and another for confirmed bugs. Otherwise it will be a real |
3 |
trouble for us to sort things out. If adding more than one keywords |
4 |
breaks anything, then I can tell you now it is already broken. |
5 |
|
6 |
The only thing that could make me thing that one keyword is enough, is |
7 |
that an actual comment is added every time a keyword is being added or |
8 |
removed off a bug, to be able to keep track of these changes. |
9 |
|
10 |
On Sat, Mar 6, 2010 at 3:45 PM, Robert Buchholz <rbu@g.o> wrote: |
11 |
> On Tuesday 02 March 2010, Sebastian Pipping wrote: |
12 |
>> On 03/02/10 20:28, Nathan Zachary wrote: |
13 |
>> >> This looks like overkill to me. One keyword should be enough, and |
14 |
>> >> for supplementary information "Status Whiteboard" could be used. |
15 |
>> > |
16 |
>> > I agree. Simply having the BUGDAY keyword should be sufficient, |
17 |
>> > and more information can be provided elsewhere in the report. |
18 |
>> |
19 |
>> If more than one keyword is commonly considered overkill I would at |
20 |
>> least request the whiteboard for it: "somewhere in the report" |
21 |
>> involves more than zero searching for it. |
22 |
> |
23 |
> Some people use the whiteboard for their own marking of bugs (e.g. |
24 |
> security, and myself). If you add more information in there, you might |
25 |
> be breaking other people's marking / sorting algorithms. |
26 |
> |
27 |
> I'd say one keyword BUGDAY is enough. Any bug editor can set and remove |
28 |
> it and the bug history will show who set and removed it when. Sorting |
29 |
> any syntax is taken care of by Bugzilla that way. It seems to me problem |
30 |
> you seem to try to solve (review of bugs) can also be tackled with tools |
31 |
> displaying new bugs that have the keyword set and just removing the |
32 |
> keyword. If bugs are repeatedly spammed with BUGDAY comments, talk to |
33 |
> the spammers or leave a comment. |
34 |
> |
35 |
> |
36 |
> |
37 |
> Robert |
38 |
> |
39 |
|
40 |
|
41 |
|
42 |
-- |
43 |
Ioannis Aslanidis |
44 |
http://www.deathwing00.org |
45 |
<deathwing00[at]gentoo.org> 0x47F370A0 |