Storybook: Storybook 3.3 Release Checklist

Created on 15 Nov 2017 · 12Comments · Source: storybookjs/storybook

Trying to get a sense of the work still left for 3.3.

Maintainers - feel free to add to this list:

[x] Alpha test
[ ] Angular support

maintenance

Source

danielduan

Most helpful comment

If we're ready, should we get a push for users to help test 3.3-alpha and release soon after then?

Some reasons why I'm pushing for this release:

There are some pretty important bug fixes that were merged to 3.3 around August/Sept and haven't gotten to users who require stable builds yet, myself included.
I'd like to alleviate the burden of having two development branches and merging between them.
The scope of the 3.3 update has been slowly expanding. I think we should define what we want in 3.3, finish it, and publish so we can move on to 3.4 and give users a more predictable release schedule.

danielduan on 15 Nov 2017

👍4

All 12 comments

Angular support

Do you mean that it also needs testing?

Hypnosphi on 15 Nov 2017

@Hypnosphi I actually have no idea what the status of it is. Is it finished and relatively stable?

danielduan on 15 Nov 2017

Should we do this checklist in the PR?

ndelangen on 15 Nov 2017

@danielduan it's merged and released as 3.3.0-alpha.3

Hypnosphi on 15 Nov 2017

I'd like to get a list of things that should happen before merging 3.3.0 into master and releasing the final 3.3.0. @ndelangen

There's lots of different discussions in different issues and PRs about what should go in here, but I think we should have a comprehensive list and get to the release sooner rather than later.

danielduan on 15 Nov 2017

We have the milestone list and it's kinda empty for now: https://github.com/storybooks/storybook/milestone/9

Hypnosphi on 15 Nov 2017

If we're ready, should we get a push for users to help test 3.3-alpha and release soon after then?

Some reasons why I'm pushing for this release:

There are some pretty important bug fixes that were merged to 3.3 around August/Sept and haven't gotten to users who require stable builds yet, myself included.
I'd like to alleviate the burden of having two development branches and merging between them.
The scope of the 3.3 update has been slowly expanding. I think we should define what we want in 3.3, finish it, and publish so we can move on to 3.4 and give users a more predictable release schedule.

danielduan on 15 Nov 2017

👍4

@storybooks/team how do we decide that alpha is tested enough?

Hypnosphi on 25 Nov 2017

I've used alpha.4 react version on my current project, works great!

ndelangen on 26 Nov 2017

I use it on mine since day one =)

Hypnosphi on 26 Nov 2017

There is also a regression that has to be fixed: https://github.com/storybooks/storybook/pull/1887#discussion_r148990688

@rhalff did you have any success with fixing it?

Hypnosphi on 28 Nov 2017

Yes I had success, the fix contained more then fixing that issue though, will try to create a pull request this week, sorry for the delay.