Attendees: Dom, Igor, Kai, Lionel, Michael, Norbert, Zol
Agenda: here
- 5.0 release: Most of SB are ready for 5.0RC "in a few days", wait and see for RN
- Projects: editor for 5.1? Typescript early but going! Presets push post 5.0, Docs mode starting
- 5.1 schedule driven release at end of Q1, experiment for the team
- Dom: Norbert and Dom pairing, a few days away
- Dom: a few days away from being green
- Norbert: what about the rest of the Storybook docs? How do we serve the docs and new website in one site? => Michael, Norbert, Tom
- Michael: We need to "formally" support presets to solve an unintended regression for advanced users in 4.1, what do we do in 5.0?
- Michael: Propose we do nothing, do the rest of packaging later after
- Igor: We need to remove warning for local configuration => Michael TODO
- Igor: Need a few days with Norbert pairing
- Michael: Need to split out RN?
- Igor: Maybe the current set of changes solves the problems that were raised a year ago
- Norbert: splitting out the package is a breaking change in RN, possibly in Web also
- Lionel: Monaco needs special webpack DLL config allows ??? => Targeting 5.1?
- Lionel: How to lighten the bundle?
- To discuss with Norbert
- Kai: More packages moving over by commmunity = great sign
- Kai: Working on babel typescript (moving everything over from tsc etc. (except Angular)) => simplifies the setup
- Norbert: Everything under eslint (not tslint)
- Michael: TS coming into new UI also
- Norbert: transformed core, not merging the PR, split up PR and merge it piece-by-piece in 5.1 => 11%, project "will be TS" after merging (new inter)
- Lionel: Story source - need the channel types to be aligned to migrate the addons?
- Norbert: Can go both ways - addon needs can drive types in core etc.
- Michael: Docs PR in progress, needs more example presets that we can point people at (revive preset repo)
- Norbert: Want recommended preset:
preset-env(Make zero-config)
- Michael: How about a schedule-driven release (end of Q1)?
- Zoltan: How about quarterly? Sounds like a good cadence for the project
- Igor: Maybe not so many big changes coming, so this could work
- Norbert: Force to downscope and release in time? Lots of chaos with lots of contributors and want to get stuff out sooner?
- Kai: Release minor changes as they come to amortize the risk?
- Michael: We need a QA process, and we want to keep the tool stable/trustworthy for our users. Will be beefing up the RC process in future releases to try to address this more
- Dom: Time-boxing also helps the release engineering