Third iteration of the Storybook release process (v1, v2), updated to reflect learnings through the 3.x release cycle.
- We respect semver for all releases to the best of our ability
release/x.y
(e.g.release/3.4
) branch is released as a patch every week (e.g.3.4.X
)master
is released on thealpha
tag every week (e.g.4.0.0-alpha.X
)- All major/minor releases get a blog post (e.g. 3.2)
We ask contributors to blog about the headline feature they've contributed once the feature is considered stable. These posts will refer to the alpha release, and:
- Allow community members to promote their work and themselves
- Help us get feedback on the individual features while the release is still in alpha
- Help us get more people using other alpha features
- Make sure we have a continuous stream of publicity around Storybook
- Make sure we have lots of content that we can refer to in the release post
Before we do a proper major minor release we:
- Update the feature posts to refer to the full release
- Document the release in a release post that highlights all the feature posts