Hi all,
I’m sorry it’s taken so long to come back to this topic. We haven’t been ignoring it. Chris, the SonarQube Product Manager, made an official announcement today:
I do want to respond here to a couple points he doesn’t address directly:
Your ability to implement/maintain custom rules should be unchanged. I believe we’re still exploring how best to communicate changes in the underlying analyzers from SQ version to version (we certainly don’t want to dump all the tickets into a single Jira repo!). But you should still have access to the same level of information about API changes.
One of the things this policy shift does is allow us to evolve a little more swiftly, so it’s possible that there could be some API changes that affect you, but I currently don’t anticipate much there.
I understand. There are certainly trade-offs. We do believe that in the end this makes the most sense for everyone involved.
You’ll need to do the SQ upgrade to get the language changes. 
We have no current plans to increase the SonarQube release cadence.
Actually, I believe the plan is to do bug-fix releases of the LTS itself. And for your example @Rebse, it would be a bug-fix version of latest.
HTH,
Ann