No matter how established a language, there’s always more issues than there are people who can work on and review them. It’s not a great feeling when issues relevant to you are not as prioritized, but that doesn’t imply neglect. We got typed globals and
const fields in mutable types in 1.8, we got native code caching and an interactive thread pool in 1.9, we’re scheduled to get multithreaded GC in 1.10. It made sense these big things had priority.
We can mitigate this with more contributors and trusted reviewers, which I think could be taught or at least set some guidelines beyond “open an issue.” For example, despite how often I chime in on issues, I am not confident enough in my testing practices to do more than spotting problems, and I wouldn’t even know what a proper documentation edit would look like. It’s legitimately more intimidating because incorrect changes to the source material can cause more widespread problems than incorrect opinions on a discourse thread.
That said, there’s never going to be enough people to cover all the issues. Look up a language of any note on Github, there are thousands of open issues, some over a decade old, and a good chunk of them are bugs and incorrect results. Always a struggle to get enough people to fix one small piece of the world, software isn’t any different.