4 ms·
Is there a way to "bump" bug reports responsibly? For example, the proposal for persistent app-tabs (https://bugzilla.mozilla.org/show_bug.cgi?id=551849 https:/
by voltagex_ 13y ago
Is there a way to "bump" bug reports responsibly? For example, the proposal for persistent app-tabs (https://bugzilla.mozilla.org/show_bug.cgi?id=551849 https://bugzilla.mozilla.org/show_bug.cgi?id=551849) seems to have stalled and the original creator now works for Google.
- cpeterso 13y agoThe best way to call attention to an inactive bug is to email the dev-platform mailing list: https://lists.mozilla.org/listinfo/dev-platform https://lists.mozilla.org/listinfo/dev-platform
- voltagex_ 13y agoThanks, how did you find out this was the right place?
- nnethercote 13y agoWorking at Mozilla for a while helps :)
- piyush_soni 13y agoThis is a relatively very new bug in Mozilla world it seems. :) See this for example, a 12.5 years old Firefox bug. https://bugzilla.mozilla.org/show_bug.cgi?id=78414 https://bugzilla.mozilla.org/show_bug.cgi?id=78414 Almost all major browsers suffered from this at a time, but the rest of them fixed it. The only important update they've done so far about this bug is to block unhappy users to even comment on it ;)
- voltagex_ 13y agoI am fully aware of the issues with Mozilla's bug tracker, that's why I asked if there was a proper way. For your bug, there's a proof of concept patch https://bugzilla.mozilla.org/show_bug.cgi?id=78414#c657 https://bugzilla.mozilla.org/show_bug.cgi?id=78414#c657
- piyush_soni 13y agoYeah, people have historically added patches, but all of them have been rejected so far for one or the other reason. They are not even willing to add an about:config workaround for that. Anyway, I'm sidetracking a lot from the subject :).
- JohnTHaller 13y agoRestricting comments so the 405 developers don't get spammed "me too", "please fix this ASAP", etc is a good thing. Bug report comments are not the place to add such things. Votes were implemented for that.
- piyush_soni 13y agoAbsolutely certainly, the voting system isn't working - and the biggest evidence of that is this bug's life span. If it had any effect at all, a vast majority of all of their (human) resources would be devoted to fixing this, since it has one of the greatest number of votes. And that is exactly the point of frustration of most of the people commenting there. I understand the "people work voluntary" reasoning, but you can't use that reason all the time. A better way to fix comments is always to have a vote up/vote down system, rather than disabling it altogether. The website already allows to selectively unsubscribe from emails for each bug for those who don't want.
- JohnTHaller 13y agobugzilla is not a public forum. There are public forums for those types of discussions. Bugzilla (and similar) is for bug reports, analysis, patches, and constructive discussion. There's no need for an up/down vote system to deal with comments that shouldn't be there in the first place. They add absolutely nothing to the developer discussion in working on a bug. Any posts of that nature should always be removed/banned in a bugtracker so developers and proper testers can get their work done.
- voltagex_ 13y agoThe problem is that the people in the know don't browse the forums where people need to know! [1] What do we do about bugs that sit there for a very long time? They're clearly not good for the developers or the community at large. [1]: https://news.ycombinator.com/item?id=6712687 https://news.ycombinator.com/item?id=6712687
- 13y ago