ST is quite likely the most cautious product I've ever seen. Most products have a development cycle like this:
[beta][stable release][active development][extended support][eol]
ST seems to call the entire period through active development "beta".. and then when they've finished developing the entire thing and hit what would normally be the extended support period (bug fixes only), they call it stable.
It's certainly costing them money. And reducing the value of licenses (since its "stable" for a shorter period of time)
If I were them, I would wait a couple of weeks (so that they get the entire benefit from their announcement today of this new build), and then re-release their software as stable -- even if no changes were made to it during that period.
This thing has been in beta since 2013. It's been tested enough. It's ready.
(And to ST: if you want free advice on your release process, you're more than welcome to email me. Or at least talk/consult with someone with product management experience.. your software is great, but this release process needs to be fixed.)