Skip to content

Instantly share code, notes, and snippets.

@shilman

shilman/RELEASE_v5.md

Last active February 16, 2019 02:08
Show Gist options
  • Save shilman/f49cbd1e05a8c4f1f9d530057841d1ee to your computer and use it in GitHub Desktop.
Save shilman/f49cbd1e05a8c4f1f9d530057841d1ee to your computer and use it in GitHub Desktop.
Download ZIP
Raw
RELEASE_v5.md

Storybook Release Proposal v5

Fifth iteration of the Storybook release process (v1, v2, v3, v4), updated to reflect learnings from the 4.1 release.

What we're doing now

  • We respect semver for all releases to the best of our ability
  • master is released on the latest tag every week (e.g. 4.0.2)
  • next is released on the next tag every week (e.g. 4.1.0-alpha.X)
  • Bugfixes and docs changes cherry-picked from next to master on every release
  • All major/minor releases get a blog post (e.g. 3.2)
  • 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

Proposed changes

  • T-2wk = feature freeze
  • T-1wk = release RCs and call for testing
  • T-0 = release but don’t announce
  • T+1d-1wk = release post + promotion
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment