- 3.0 release retrospective:
- what went right/wrong?
- References
- Semver
- breaking changes (e.g.
marksy
) => 3.1
A Storybook release process based on Semver. In short:
- merge bugfix PRs directly into master automatically release (~daily)
- merge feature and breaking PRs into a release branch (e.g.
release/3.2
) and release features in groups along with a marketing push after a preview period (~monthly)
During the Storybook 3.x transition we've undergone a series of growing pains as we've opened up the development process. We've had questions about:
Goals:
- Docs for the latest stable release of Storybook, statically hosted at https://storybook.js.org
- Docs for a preview release, clearly labeled as
preview
with disclaimers and pointers to the main docs - Docs for previous minor releases of Storybook, with disclaimers and pointers to the main docs
Patterned off of Meteor docs site (source)
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.
Attendees: Norbert, Filipp, Chak Shun, Wei Wei, Neville, Gytis, Zol, Michael
Rough agenda: https://gist.github.com/shilman/815fe665614f552d72c504f357d6c6b1
Recorded video: https://www.youtube.com/watch?v=KnCV_Wu8Rbs&feature=youtu.be
- Filipp: Update the release process after 4.0:
- release 4.0 off
master
Wwhat I did to manually test some breaking changes to @storybook/cli
by publishing a test
-tagged package to NPM.
Publish package:
yarn bootstrap --reset --core
cd lib/cli
# edit package.json version: 4.0.0-alpha.24 => 4.0.0-test.25
npm publish --tag test --access public
Fourth iteration of the Storybook release process (v1, v2, v3), updated to reflect learnings from the 4.0 release.
- 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
)