> On Feb 10, 2022, at 11:55 AM, Brent Fulgham via webkit-dev > <webkit-dev@lists.webkit.org> 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
