Skip to content

Latest commit

 

History

History
118 lines (86 loc) · 6.7 KB

RELEASES.md

File metadata and controls

118 lines (86 loc) · 6.7 KB
Raw

Release Process

A Storybook release process based on Semver. In short:

  1. Merge all PRs into next, which is the default branch. Cherry-pick bugfix PRs into master, which is the stable release.

  2. Every week: release patch releases off master to the NPM tag latest, and alpha releases off next to the NPM tag next (as e.g. 4.1.0-alpha.0).

  3. Every month or two, merge next into master and release a minor/major version according to semver. We set minor release dates as soon as we have feature clarity and manage to those dates:

    • Date should be a Monday so if we slip we don't get pushed into the weekend
    • T-3wk:
      • Draft announcement and socialize
      • Announce dates in #maintenance so people can react
    • T-1wk:
      • If you want your feature in the release, it should already be released on next by this time
      • Create release branch and only cherrypick bugfixes
      • Set up launch plan

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:

  1. how to adhere to semver?
  2. how to do marketing releases (while adhering to semver)?
  3. how to introduce significant new features (e.g. vue support, story hierarchy)?
  4. how to converge on key design decisions (e.g. new addons API)?
  5. how to schedule releases?
  6. how to maintain quality/stability through the process?
  7. how to pay down tech debt as we go?

This process attempts to address all these concerns in one shot.

Semver

Semver dictates three types of release:

  1. MAJOR version when you make incompatible API changes,
  2. MINOR version when you add functionality in a backwards-compatible manner, and
  3. PATCH version when you make backwards-compatible bug fixes.

We'll do our best to adhere to Semver, but won't be religious about it. In particular, we may occasionally release small bits of new functionality in PATCH releases. We'll try our best to restrict breaking changes to MAJOR releases.

PATCH releases

Every bugfix should go out as soon as we've verified the fix, and based on the current rate of contribution, we should be issuing PATCH releases weekly. Eventually, we'll automate the process so that a release will go out every time a PR is merged into master, and we've already laid most of the groundwork for this.

MINOR releases

Every new feature, particularly significant ones (e.g. Vue support, deep hierarchy for stories) deserves more attention:

  1. They should be well-tested by the community before we release.
  2. They often have architectural implications for the entire Storybook ecosystem, so should be discussed thoroughly before release. Doing alpha releases allow us to test in the community without necessarily achieving agreement.
  3. They often deserve proper marketing treatment (blog posts, release announcement, podcast, etc.)

Therefore we release alpha versions continuously on the NPM next tag to allow people to test out features as soon as they are ready.

In general, we should release 2-3 headline features per minor release for marketing purposes. Each headline feature should get its own blog post on the Storybook medium publication, and the release itself should also get a blog post.

MAJOR releases

We should avoid major releases, but won't hold ourselves back on this. Making storybook better is the prime directive, and if we have to make breaking changes to do it, we will. That said, MAJOR releases should have killer features that reward users for upgrading, and should not be used to scratch our own architectural itches -- unless those itches are really killing development in some meaningful way.

Blocking bugs

Most PATCH releases come from community members, who generously fix problems as they come up. However, there are also bugs that never get picked up and just sit there gathering upvotes and "me too" comments. We need a way to make sure that these bugs get addressed.

For every non-PATCH release, we nominate a small number of bugs that must be addressed before a release can go out by adding them to the milestone. For example, here's a list of blocking bugs for the 3.2 milestone.

Adding bugs to the milestone helps people looking for good ways to contribute, or to understand what is blocking the release so they can actually do something about it. Discussion about which bugs are critical happens in the #maintenance channel in our Slack Storybook Slack

If you're experiencing a bug, the best way to make sure that it gets attention is to upvote it by adding a "thumbs-up" reaction in Github. This way important bugs quickly bubble to the top with a search.

The best way to make sure a bug gets addressed quickly is to fix it yourself and issue a PR. If the fix is good, we'll try to release it quickly in a patch release.

Decision-making

  • For PATCH changes, all discussion can occur in issue/PR comments (and random slack chat as needed).
  • For MINOR feature changes, there are multiple stages of discussion:
    • The feature may be discussed in an issue before it is implemented (ex: #151)
    • Once it's implemented, the discussion may occur on the PR (ex: #1329)
    • If people disagree on an implementation and it can't be resolved in discussion, they may issue alternative PR's with different ideas
    • Ultimately the maintainers will reach a consensus before merging the changes. There is no set process for this, but we're all adults.
    • Since MINOR features are released in alpha before they are fully released, new issues may be created by end users, etc.
  • For MAJOR infrastructural changes, the discussion may take place over time, in gists, issues, slack discussions, etc.
    • Once the breaking changes have been reduced to an actual implementation, it looks pretty much like a feature release (only with higher stakes and probably a longer stabilization process).

FAQ's

How does my PR get merged?

  • For PATCH PR's, any maintainer can review, test, approve, and merge it.
  • For MINOR/MAJOR PR's, once a maintainer reviews, tests, and approves it, s/he should clear it with the other maintainers before merging it into the release branch.
  • Once a release date has been set and we cut off merging, we'll create a temporary branch to hold that release so that it doesn't block merging to next.