In the Internet era it doesn't make sense to have major software releases. You can release early and often. Release MVPs.
In the old days where release meant producing tapes/floppies/CDs, putting them in boxes and shipping by trucks, it required having major changes to sell, and completely finished features.
But now, if you go for release-often-mvp philosophy, you don't have opportunity for a big marketing announcements.
@kornel One strategy is to ship the features continually and then announce them to the press later. It’s ok if existing customers enjoy them earlier. The press moment is to attract new customers.
@jeremiahlee Rust has this problem. There's a small release every 6 weeks. They tried to have a fanfare re-release of already-released features (AKA Rust 2018), but it caused confusion: what actually was released in a new version, what was old, how fast is the language actually changing, etc.
@kornel Ah yeah, in a programming language or protocol, this strategy would be bad.
Ember.js solved a similar problem with "editions". https://emberjs.com/editions/
