[webkit-dev] Bug life cycle

[David D. Kilzer]

There are a couple of fairly old bugs (2001) for Bugzilla on http:// 
bugzilla.mozilla.org/ for creating custom resolutions and custom  
statuses:

Customized resolutions.
https://bugzilla.mozilla.org/show_bug.cgi?id=94534

Customized statuses and workflow
https://bugzilla.mozilla.org/show_bug.cgi?id=101179

Looks like there has been some recent activity on both of them.

Dave


On Nov 14, 2005, at 6:08 PM, Dan Udey wrote:

> After a bit of experimentation with the latest (2.20) release of  
> Bugzilla, I've discovered that adding/removing/modifying the list  
> of resolutions in Bugzilla is, apparently, non-trivial. The all- 
> caps identifiers (e.g. 'FIXED', 'WONTFIX', 'WORKSFORME', etc.) are  
> hard-coded into several places in the tree, as well as (for some  
> reason, most likely ordering and enablement) in the database table  
> 'resolution'. Adding them to the database merely results in a blank  
> string in the Bugzilla interface.
>
> It looks like adding different resolutions might not be the best  
> solution. The change would be relatively easy for anyone who knows  
> Perl well enough, but it would be non-trivial, and would affect the  
> entire OpenDarwin project, so a  unilateral solution might not be  
> the best. Any other ideas?
>
> On 14-Nov-05, at 3:34, Joost de Valk wrote:
>> On Nov 14, 2005, at 8:01 AM, Maciej Stachowiak wrote:
>>> On Nov 12, 2005, at 6:51 AM, Joost de Valk wrote:
>>>> Hi all,
>>>>
>>>> today, while talking on #webkit, i got two questions which both  
>>>> should be answered in the bug life cycle document on the WebKit  
>>>> page as well, in my humble opinion. To be able to do that, i'd  
>>>> like to get some consensus on them.
>>>>
>>>> The first one, brought up by Alexey Proskuryakov (ap), is this:  
>>>> when a bug can't be reproduced anymore but has been confirmed at  
>>>> one point in time, what to do with it? My answer for this would  
>>>> be to close it as "WORKSFORME" and not as "FIXED", since you  
>>>> don't know what fixed it. Ideally we would create a new  
>>>> resolution for this, something like "FIXED WITHOUT SOLUTION" or  
>>>> something like that, have you people perhaps got any thoughts on  
>>>> this?
>>>
>>> How about "PRESUMED FIXED". I also wish we could get the  
>>> ALLCAPSSINGLEWORD style out of the resolutions. Not sure how hard  
>>> this is to do without hacking the database. Something that is  
>>> believed fixed by an unknown change is indeed different than  
>>> something that couldn't be reproduced at all, although  
>>> "WORKSFORME" arguably could cover both bases. "PRESUMED FIXED"  
>>> would indicate to the verifier that they must verify with a more  
>>> recent version, and would indicate to integrators that if they  
>>> want to ship the fix on a branch version, they have to hunt for it.
>>>
>>
>> This is fine by me, getting rid of the all caps would be great,  
>> but i don't know if we break any external apps by doing that?
>