Skip to content

Commit e2fcb53

Browse files
committed
Add the "Release Process" page
1 parent 50a731c commit e2fcb53

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

Release Process.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
2+
The Git workflow used in this project is largely inspired by [Gitflow workflow]()(https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow).
3+
4+
* The development branch is `dev`
5+
* When releasing a new **patch** version:
6+
* Cherry-pick the necessary commits to the `master` branch
7+
* Push to GitHub, make sure all CI tests are passed, and then run `yarn release` in the project root
8+
* Draft a new **release** in the GitHub [Releases](https://github.com/vuejs/vue-cli/releases) page
9+
* Merge `master` back into `dev`
10+
* When releasing a new **minor/major** version
11+
* Cherry-pick the necessary commits to the `next` branch
12+
* Push to GitHub, make sure all CI tests are passed, and then run `yarn release --dist-tag next` in the project root
13+
* Draft a new **pre-release** in the GitHub [Releases](https://github.com/vuejs/vue-cli/releases) page
14+
* If no urgent regressions have been reported in **3 days**:
15+
* run `npm dist-tag add {{package-name}} latest` for all the packages in this repository
16+
* Go to the Releases page and uncheck the `This is a pre-release` option for this release
17+
* Otherwise, fix the bugs, and start over to release a new version from the `next` branch. But this time the new version string should be bumped as patch.

0 commit comments

Comments
 (0)