Also, inevitably some people in good faith will believe they find a bug when something doesn't work the way they expect it to behave. You can't expect everyone to follow all discussions about features getting cut, so a link to whatever discussion there was (if ever) would have been appropriate.
Do users post to the firefox bug tracker when features are removed like in the gnome case ? How is it handled ?
Apparently, this behaviour was considered a bug, if a very long-lived one. So a recent update 'fixed' that behaviour, although the justification is stronger there, and the workaround (SuperStop addon[2]) is actually useful, although still on a different keybind (Shift-Esc)
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=825486
[2] https://addons.mozilla.org/en-US/firefox/addon/superstop/
The reason you have these discussions on the issue tracker is so when the next person comes along to file the issue, he/she now has the relevant context. Randomly guessing at which group to search and post to hardly helps in discovery. If you don't want discussion, disable the comments. But that's hardly conducive to good community teamwork.
And I'm really not aware of any project that only uses a "bug tracker." They almost all track issues, ranging anywhere from bugs to new feature requests. Maybe Gnome is different in this regard, but I don't think it's crazy for someone to believe otherwise. Redirecting conversation smacks of a "bugger off" mentality.
I might be naive about collaborative software development or the way gnome dev handle things but I think bugtrackers should be about bugs and technicalities, not feature approval or UX discussion if user feedback is wanted otherwise everything that a given user finds annoying would be considered a "bug" and drama would occurs.
This "talk" is more shocking in my opinion than the one that made the headline.
Yes, the original answer is "just" missing the link. As is also the answer to the why comment.
It's not a bug, it is the removal of a feature. Is a bug tracker really the most appropriate place to discuss in which direction a software is to go ?
'No' and a link to the relevant reason and workaround should be fine in that case but apparently that had already been discussed before (and a reason was given).
I don't know if removing it through so much commits is good practice but if the feature was to go it doesn't make a difference in the end, he sculpts his piece of the software any way he likes it as long as it's feeature oriented, right ?
Note: I have no advice on wether that feature should have been removed or not in the first place.