| 1 |
Duncan wrote: |
| 2 |
>> 2. Be careful with INVALID resolutions |
| 3 |
>> |
| 4 |
>> The term invalid _is_ harsh in bugzilla context, so make sure you write |
| 5 |
>> a quick thankful-sounding comment to go with it. |
| 6 |
> |
| 7 |
> I like all the suggestions, but this one hits a particular sore spot, as I |
| 8 |
> had it happen to me, with I think my second Gentoo bug filing. |
| 9 |
|
| 10 |
I'm glad that you can relate to it - reassures me that I'm not pulling |
| 11 |
this out of thin air :) |
| 12 |
|
| 13 |
> What made |
| 14 |
> things worse is that the filing was after my arch team had asked for |
| 15 |
> volunteers to perform specific tests (multilib-strict), and I had gone to |
| 16 |
> significant effort to do so, having builds die that would otherwise have |
| 17 |
> completed successfully. |
| 18 |
> |
| 19 |
> As it happens, the bug /was/ valid, and was eventually resolved |
| 20 |
|
| 21 |
That's another issue which is worth thinking about. I'm just as bad at |
| 22 |
this myself - if I can close a bug report without doing any work (i.e. |
| 23 |
the case for most INVALID bugs) then it's almost like a small personal |
| 24 |
victory. |
| 25 |
|
| 26 |
We should also try not to jump the gun so much in this kind of situation. |
| 27 |
|
| 28 |
Thanks for the feedback, if bugzilla ever drives you to suicide I will |
| 29 |
be sure to file a bug report at the official Bugzilla bugzilla so that |
| 30 |
it can be corrected :) |
| 31 |
|
| 32 |
Daniel |
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives