Release workflow

Describe branches' role & workflows for releases by types.

Branches

• latest: latest tag
• next: next tag
• master: primary branch

  In order to have control over the timing of releases,
  "release" will be triggered from the latest or next branches only.

  • Triggering a release

Workflow

All devs will be done on master.

nightly will merge changes from master and build nightly dist at the day when found changes on master.

• RC release: master → next

  master will be merged into next branch.
  Every updates before the latest, should flows from master to next.

  Will publish @next by semantic-release

• Patch release: master → latest

  master will be merged into latest branch.

• latest(stable) release: master → latest

  • If all issue resolved or no issue found from the next release, will proceed the latest release.

    The period between 'next' to 'latest', not precisely defined, but roughly in a period of 1w ~ 3weeks.

  • master will be merged into latest branch.

    Will publish @latest by semantic-release

Schedule

Minor

The intended schedule for official release is on every 3 months.

Note: The period is not an exact & definitive.

Patch

Whenever and according the importance, the patch will be released when is necessary.