-
Notifications
You must be signed in to change notification settings - Fork 358
Release workflow
Jae Sung Park edited this page Jun 25, 2019
·
23 revisions
Describe branches' role & workflows for releases by types.
- latest: latest tag
- next: next tag
-
master: primary branch
In order to have control over the timing of releases,
"release" will be triggered from thelatestornextbranches only.
All devs will be done on master.
nightlywill merge changes frommasterand buildnightly distevery day.
-
masterwill be merged intonextbranch.
Every updates before the latest, should flows frommastertonext.Will publish @next by semantic-release
-
masterwill be merged intolatestbranch. -
nextwill be merged intolatestbranch.Will publish @latest by semantic-release
- Why we decided to start billboard.js?
- Comparison table
- How to migrate from C3.js?
- Who's using billboard.js
- Third party applications
- Themes
- Roadmap
- Architecture & Event
- Plugin Interface
- Release workflow
- How behaves for dynamic loading?
- How tooltip behaves on grouped option?
- How to load as ESM directly from the browser?
- How to implement realtime chart?
- How to bundle for legacy browsers?
- How to generate chart image in Node.js environment?
- Understanding padding