Re: [webkit-dev] Proposed changes to Bugzilla 'Resolution' categories

[Sam Sneddon via webkit-dev]

Note we do have documentation of what they mean at 
https://webkit.org/bug-life-cycle/ , though 
this already appears to be incomplete (e.g., we have "CONFIGURATION CHANGED”, 
which I don’t know how people are meant to know what that means… what 
configuration?).

/Sam

> On 10 Feb 2022, at 20:11, Tim Nguyen via webkit-dev 
>  wrote:
> 
> Hi!
> 
> Pretty sure WORKSFORME corresponds to “Behaves As Designed”, that’s how 
> Mozilla’s bugzilla’s instance uses it at least.
> 
> Adding new resolution statuses seems fine, but maybe old ones (WORKSFORME, 
> WONTFIX, INVALID, etc.) should be cleaned up/migrated too, otherwise folks 
> (coming from other OSS projects using Bugzilla) will still keep using them. 
> Maybe they could be disabled.
> 
> -Tim
> 
>> On 10 Feb 2022, at 20:55, Brent Fulgham via webkit-dev 
>> mailto:webkit-dev@lists.webkit.org>> wrote:
>> 
>> 
> 
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Proposed changes to Bugzilla 'Resolution' categories

[Alexey Proskuryakov via webkit-dev]

> 10 февр. 2022 г., в 12:06 PM, Michael Catanzaro via webkit-dev 
>  написал(а):
> 
> On Thu, Feb 10 2022 at 11:55:56 AM -0800, Brent Fulgham via webkit-dev 
>  wrote:
>> (1) Add a new “Behaves As Designed” option:
>>> This will represent bugs that were filed when the reporter misunderstands a 
>>> feature, or wants behavior that we have considered, but chosen not to allow.
>>> This would be used instead of the somewhat offensive “WONTFIX” or mildly 
>>> offensive “INVALID” resolutions we currently use.
> 
> I'm surprised we don't already have an appropriate status for this, 
> considering how common it is. Calling this NOTABUG would match at least one 
> other major Bugzilla instance, and is nice and short. Alternatively, we could 
> call it EXPECTED BEHAVIOR. BEHAVES AS DESIGNED seems a bit long.
> 
>> (2) Add a new “Platform To Resolve” option:
> 
> Like Simon, I currently use the existing MOVED status to indicate this 
> ("Moved" to external tracker), although it's not a perfect fit if I simply 
> tell the reporter to report elsewhere (in that case, it really means "needs 
> to be moved"). If we want to add another status for this, we should look for 
> a simpler name.


There are two different cases here, which should probably have different 
resolutions.

1. The resolver determines that this is not a WebKit issue, and wants to the 
reporter to file it against the platform. This is generally the most helpful 
thing to do for Apple platforms, because it creates a line for communication 
between Apple and the reporter. Migrating it ourselves may feel like it would 
be best, but in my opinion at least, it's not.

2. The resolver determines that this is not a WebKit issue, and reports it 
against the platform (or finds an existing platform bug report).

- Alexey
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Proposed changes to Bugzilla 'Resolution' categories

[Tim Nguyen via webkit-dev]

Hi!

Pretty sure WORKSFORME corresponds to “Behaves As Designed”, that’s how 
Mozilla’s bugzilla’s instance uses it at least.

Adding new resolution statuses seems fine, but maybe old ones (WORKSFORME, 
WONTFIX, INVALID, etc.) should be cleaned up/migrated too, otherwise folks 
(coming from other OSS projects using Bugzilla) will still keep using them. 
Maybe they could be disabled.

-Tim

> On 10 Feb 2022, at 20:55, Brent Fulgham via webkit-dev 
>  wrote:
> 
> 

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Proposed changes to Bugzilla 'Resolution' categories

[Michael Catanzaro via webkit-dev]

On Thu, Feb 10 2022 at 11:55:56 AM -0800, Brent Fulgham via webkit-dev 
 wrote:

(1) Add a new “Behaves As Designed” option:

This will represent bugs that were filed when the reporter 
misunderstands a feature, or wants behavior that we have considered, 
but chosen not to allow.


This would be used instead of the somewhat offensive “WONTFIX” 
or mildly offensive “INVALID” resolutions we currently use.


I'm surprised we don't already have an appropriate status for this, 
considering how common it is. Calling this NOTABUG would match at least 
one other major Bugzilla instance, and is nice and short. 
Alternatively, we could call it EXPECTED BEHAVIOR. BEHAVES AS DESIGNED 
seems a bit long.



(2) Add a new “Platform To Resolve” option:


Like Simon, I currently use the existing MOVED status to indicate this 
("Moved" to external tracker), although it's not a perfect fit if I 
simply tell the reporter to report elsewhere (in that case, it really 
means "needs to be moved"). If we want to add another status for this, 
we should look for a simpler name.


Michael


___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Proposed changes to Bugzilla 'Resolution' categories

[Simon Fraser via webkit-dev]

> On Feb 10, 2022, at 11:55 AM, Brent Fulgham via webkit-dev 
>  wrote:
> 
> Hi Floks,
> 
> I would like to propose some changes to the categories we use to resolve 
> bugs. I’ve been trying to do some Bugzilla gardening to better reflect the 
> state of various “edge case” bugs that often leave users confused about the 
> state of issues they’ve reported, and unsure of whether fixes are needed or 
> have been shipped.
> 
> Some of this is due to inertia, but some is due to lack of clarity in how to 
> treat a few categories of bugs.
> 
> (1) Add a new “Behaves As Designed” option:
> 
> This will represent bugs that were filed when the reporter misunderstands a 
> feature, or wants behavior that we have considered, but chosen not to allow.
> 
> This would be used instead of the somewhat offensive “WONTFIX” or mildly 
> offensive “INVALID” resolutions we currently use.

I like.

> 
> (2) Add a new “Platform To Resolve” option:
> 
> This will represent bugs that are actually in an underlying component outside 
> of sources in the WebKit project. This might be used to represent graphics 
> driver bugs, kernel issues, platform User Interface libraries, or most 
> frequently bugs in applications driving WebKit.
> 
> This would be used instead of the somewhat offensive ‘INVALID” resolution.

I've used RESOLVED/MOVED for this, which seems reasonable (though the MOVED is 
pretty vague: moved where?).

Simon

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev