Storybook 4.x roadmap discussion

discussion.md

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
   1. breaking changes (e.g. marksy) => 3.1
   2. addon breaking changes (e.g. vue => addon-notes)
   3. "transitioning to semver"
3. Key problems:
   1. User problems
      1. webpack
      2. react native
      3. info addon?
   2. Developer problems
      1. lerna / npm
      2. CONTRIBUTING.md
      3. test coverage / release confidence
      4. CI bloat?
4. Next release: features
   1. Vue
   2. Addons updates (info, API for extra info)
   3. Info addon => panel
   4. Story hierarchy?

Possible we could start discussing development workflow and put it to CONTRIBUTING.md. E.g. for big features it could look like that:

• pick a point from our roadmap

• create an issue with the new feature description and a short explanation how it's going to be implemented. if it is needed
  add steps to divide this work

• create a new branch for this feature

• submit one or more PRs to this brunch

• after work was finished add docs and tests for this feature

• merge feature-branch to master (or to nextV4-branch?)

Some notes (unstructured)

attendees: @usulpro @ndelangen @trevoreyre @shilman

semver

• try to stick with it from now on

roadmap

• link to issues
• add note to contact maintainers

addon api

• conditional panels that only show up when there's content in that panel
• show multiple addon panels at once (e.g. info addon => readme + props addon)
• show multiple story previews at once (n-up views)

better examples

• styleguide: lonely planet?

document

• feature development workflow
• npm run dev

build times

• remove test-cra will improve
• remove docs bootstrap? - split it out somehow?
• RN stuff in separate CI?

test coverage

• cypress.io end-to-end testing
• snapshot testing
• high coverage for new work
  • vue
  • addon api changes