Incorrect. Change is implemented only in tests-passed… be on Stable or Beta if you don’t want experimental changes. What you’re asking for already exists.
I’d say you need to be active on at least 5 different reasonably sized Discourse instances to have enough data. (Not including meta, since meta is kind of a dodo bird in terms of feedback, it’s not really representative.) The team is unique in that we sit at the confluence of probably 100+ Discourse instances, of which I touch at least 10 per day, and probably see up to ~20 on any given day, including weekends.
There’s a serious “sample size of one” problem that you want to avoid. Your particular community may have certain… predilections and quirks… that perhaps may not be shared by many other communities. But from this vantage point, we see everything – we’ve read literally every single meta post since Feb 2013, most meta discussion that occurs on other active Discourse instances, and we sample ~10-20 Discourse instances every day, Monday through Sunday, every week, for the last year and a half.
Inevitable with this highly complex stack – show me another all-JavaScript project running Ember.JS and Rails that has any kind of open source traction.
And to be honest right now I do not care at all about developer adoption, we need customer adoption over the next 12 months if we want the project to survive. Period.
Trends look reasonably good, don’t get me wrong, but the priority is on project survival via customer happiness, not any abstract metrics of developer happiness.