3 ms·

I would agree, but I would also say that they should err on the side of caution. Don't see all of these posts and just call the next release 3.0. Do an absolute

I would agree, but I would also say that they should err on the side of caution. Don't see all of these posts and just call the next release 3.0. Do an absolute thorough round of testing. Be sure that it is stable. Then bring it out of "beta". As bad as breaking the beta would be, releasing a product after such a long beta period that isn't completely stable would be worse. All that said, Sublime is easily the most stable piece of software I use on a daily basis. I prefer JetBrains IDEs for daily coding, but still do plenty of work in ST3 and have customized the heck out of it to fit my needs almost perfectly. I'd be very much surprised if it wasn't ready to exit beta today

rgbrenner 9y ago
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.)

3 ms·

I would agree, but I would also say that they should err on the side of caution. Don't see all of these posts and just call the next release 3.0. Do an absolute

by apocalyptic0n3 9y ago

rgbrenner 9y ago
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.)