I had a quick check and it looks like Microsoft doesn't have an automatic clean-up bot running which is really nice to see.<p>Compare it to the Istio project which just deletes your issue if someone doesn't respond it to after 28 days. Despite the issue often being quite real.<p>Also I wonder how these larger projects will fare once Github rolls out the Discussions feature.
I remember when the issue tracker for TypeScript or VSCode was still relatively new, the issue quality was much better. Now if you look at their issues, it's like trying to wade through spam, I hope they have specialized people who don't get demoralized from reading the issue list.<p>For example just one issue last hour "Slow performance" and basically list of extensions, OS info. To track that one down, they should test each and every extension listed, and still might not have a good understanding what is going on.
This is one area where I feel github is really letting us down.<p>Everything ends up in a giant "bag", where you end up with 1000+ "issues". While you can go into issues then sort by a given label, this has to be done actively, and constantly kept up to date.<p>I'd prefer something more like an 'inbox', where issues can be filed into different categories which moves the out of the 'new' section. This is what most large projects are doing anyway with labels.
I can understand why so many issues get created. I've had to read through quite a few issues for node.js debugging issues because they've made changes to the feature.<p>Before I could just do `node --inspect index.js` and get the debugger to auto attach with my node version set using NVM. There's a few different flags to try. I ended up wasting a few hours to just get debugging working again. Now I have to actually set a launch profile (I've got one which works) but wading through all the issues because they've changed, to me, a fundamental feature was just plan frustrating.
What do "dev question" and "user question" mean? Are these support questions that get asked using a GitHub Issue as the medium, rather than bug reports?
The problem is that project like VSCode racking up these bugs, and letting them to snowball. It's not that they can't sort them out with 30+ full time professional QAs at Microsoft.<p>Once upon a time, GNOME had 300 bugs in evolution bugzilla, and it was felt as "the end of the world."<p>What they need to do is just like GNOME projects a decade+ ago did: make a really hard, like HAAAARD! feature freeze, and keep doing long series of "housekeeping" releases <i>as long as needed</i> before unfreezing work on features.
The wiki is a great reference, but a search of the word "grooming" across Bing [¹], Google [²] and DuckDuckGo [³] all lead to references to child pedophilia.<p>The definition of that word is changing and not accepting that fact looks dated. Might just be my opinion, feel free to comment if you disagree.<p>[1] <a href="https://www.bing.com/search?q=grooming" rel="nofollow">https://www.bing.com/search?q=grooming</a><p>[2] <a href="https://duckduckgo.com/?q=grooming" rel="nofollow">https://duckduckgo.com/?q=grooming</a><p>[3] <a href="https://www.google.com/search?q=grooming" rel="nofollow">https://www.google.com/search?q=grooming</a>