shilman

Roadmap discussion

0. 3.0 release retrospective:
   1. what went right/wrong?
1. References
   1. Roadmap https://github.com/storybooks/storybook/blob/master/ROADMAP.md
   2. Support: https://github.com/storybooks/storybook/issues?utf8=%E2%9C%93&q=is%3Aissue%20label%3A%22question%20%2F%20support%22%20
   3. Bugs: https://github.com/storybooks/storybook/issues?utf8=%E2%9C%93&q=is%3Aissue%20label%3Abug%20
2. Semver
3. breaking changes (e.g. marksy) => 3.1

shilman

Storybook Release Proposal

A Storybook release process based on Semver. In short:

1. merge bugfix PRs directly into master automatically release (~daily)
2. 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)

Motivation

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:

shilman

Versioned Documentation for Storybook

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

Proposal

Patterned off of Meteor docs site (source)

shilman

Storybook 3.2-alpha Feedback

We're rolling out a few big features in Storybook 3.2 and need your feedback:

• Vue support
• Story hierarchy

DISCLAIMERS: Our release process is for getting new features into your hands early to stabilize things. API's may change before full release!

FEEDBACK: To give feedback on a feature comment on the open issue linked below, and be sure to include the version you're using. To give feedback on the release, feel free to comment on this gist, or come chat with us on slack.

shilman

WithX API proposal

Today's type system

type story = (context) => renderable
type decorator = (story, context) => renderable

For example:

shilman

Storybook Release Proposal v2

A Storybook release proposal that combines Semver with marketing considerations. In short:

1. multiple major versions per year
2. blog post for each major version

Motivation

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.

shilman

Storybook Roadmap Meeting 5

attendees: @danielduan, @tmeasday, @shilman, @ndelangen

Release 3.4

• feature freeze by @Hypnosphi
• 3.4 alpha out today @shilman
• 3.4 RC out this week @shilman
• letter to our medium followers, tweet for testing

shilman

Storybook Roadmap 2018-05-24

Some topics for tomorrow's meeting

• Project update
  • New contributions
  • Stats
• 4.0 Release
  • blocking
• schedule

shilman

Storybook Roadmap Notes 2018-05-24

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

shilman

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