A Storybook release proposal that combines Semver with marketing considerations. In short:
- multiple major versions per year
- blog post for each major version
Earlier this year I proposed a release strategy that attempted to reduce major versions. We've been running with that strategy for six months and have released 3.0, 3.2, and 3.3 this way, but continue to get pushback on adhering to Semver. This proposal attempts to address those concerns and is inspired by Jest's versioning.
We continue to do marketing releases of Storybook. However, these will be major releases instead of minor ones.
The approach:
- Gather 3+ noteworthy "headline" features with clear user benefit
- Publish a major release and a blog post
Under this strategy 3.2 would have been released as 4.0, and 3.3 would have been released as 5.0. In fact, technically they should have been major releases under semver since both contained breaking changes.
This approach:
- allows us to support semver more strictly
- still allows us to do marketing releases (and it's clear when)
- allows us to deprecate things more quickly and keep our codebase/documentation a lot more clean
- encourages users to upgrade to the latest despite breaking changes
Potential drawbacks:
- No way to denote huge changes (that are bigger than anything we've released so far)
- May potentially introduce major version bumps that don't contain breaking changes