I'm not sure a productive discussion can be had on such a broad topic without specific examples or suggestions :)
It's important to note, I think, that the existence of disagreements about prioritization, controversial bugs, and missed issues is an unavoidable reality of running a large, open software project. Obviously, to be a well-run project, it's important to be constantly trying to improve processes and systems to avoid missing or failing to prioritize important issues, but "importance" can be a very subjective thing, and eliminating disagreements entirely is just not possible. Gavin On Wed, Oct 29, 2014 at 3:38 PM, Drew DeVault <sircm...@gmail.com> wrote: > I was mistaken - for some reason I thought it was not fixed. Still, > though, it's a good example for the problems with bugzilla, and the > topic as a whole is still worth discussing. > > (cc: dev-platform) > > On 10/29/2014 04:38 PM, Gavin Sharp wrote: >> Hey Drew, >> >> The bug you linked to is fixed, and if all goes well the fix will be >> released in Firefox 35. Can you perhaps elaborate on why you think it >> was "incorrectly closed"? >> >> (It may be best to redirect this thread to dev.platform, since that's >> the best place to discuss bugs in platform code like that one.) >> >> Gavin >> >> On Wed, Oct 29, 2014 at 2:26 PM, Drew DeVault <sircm...@gmail.com> wrote: >>> Hey guys. I'm wondering if the process of triaging and addressing bugs on >>> Bugzilla is being handled well. Today, I found this bug: >>> >>> https://bugzilla.mozilla.org/show_bug.cgi?id=649849 >>> >>> This is not the first bug whose severity I feel has been misjudged, but it >>> is the one that made me decide to bring it up here. This bug is 3 and a half >>> years old, with 222 votes. If it weren't incorrectly closed, it would be #4 >>> on the most voted bugs in Core. It's clearly a problem and has been for a >>> long time, and the (justified) complaints about its idle state are met with >>> hostility. This bug is unique among high-voted bugs because it is low risk >>> and (presumably) easy to solve. >>> >>> I've seen other bugs like this, and I'm wondering if Bugzilla is being >>> handled appropriately. I think it's clear that this bug should have been >>> dealt with a long time ago. How are bugs prioritized and why is it the case >>> that long-standing, important bugs can fall behind so easily? What can we do >>> about it? >>> >>> -- >>> Drew DeVault >>> _______________________________________________ >>> firefox-dev mailing list >>> firefox-...@mozilla.org >>> https://mail.mozilla.org/listinfo/firefox-dev > > _______________________________________________ > firefox-dev mailing list > firefox-...@mozilla.org > https://mail.mozilla.org/listinfo/firefox-dev _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
