-
Notifications
You must be signed in to change notification settings - Fork 358
Release workflow
Jae Sung Park edited this page Jun 20, 2019
·
23 revisions
Describe branches' role & workflows for releases by types.
- master: latest tag
- next: next tag
-
dev: primary branch
Will takeover previous master branch's role.
In order to have control over the timing of releases, addeddevbranch.
All devs will be done on dev.
nightlywill merge changes fromdevand buildnightly distevery day.
-
devwill be merged intonextbranch.
Every updates before the latest, should flows fromdevtonext.Will publish @next by semantic-release
-
devwill be merged intomasterbranch. -
nextwill be merged intomasterbranch.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