Versioning Policy

Jump to bottom Edit New page

Sotaro KARASAWA edited this page Sep 5, 2018 · 3 revisions

Crowi versioning policy.

v1

Master Branch

Usually, develop Crowi on master and we follow like GitHub flow.
All feature and fix branches will be targeted and merged to master.

After `1.x` release Until it would be stable.

Master branch points to 1.x.
During the period, develop 1.x+1 on dev/v1.x+1 branch (e.g. dev/v1.8) and branches which appear for next version will be targeted to that branch.

After it would be stable

Switch development branch for next version to master, and remain a branch for 1.x to release/v1.x.

Versioning Tag

Tag v1.x.y after the branch is ready for release.

Hotfix

Fix some bugs or security issues would be merged to release/v1.x and tagged on that branch.

v2

Re-architecture
SPA + SSR