You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 26, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: docs/guide/basics/release-cycle.md
+29-3Lines changed: 29 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
This document describes how Vue Storefront code versions are released. You'll learn how the release process looks like, what are the acceptance criteria, what is our git flow and which branch to use as a stable one.
4
4
5
-
# How Vue Storefront versions are released
5
+
##How Vue Storefront versions are released
6
6
7
7
From version 1.9 we release each of VSF versions in two phases
8
8
-**Release Candidate phase (RC)** also called "feature version". This version contains all the new features, improvements and additions to the API along with minor bugfixes. New features and additions are merged and released **only** during this phase. The API of features introduced during this phase may slightly change.
@@ -12,9 +12,35 @@ So assuming next version is 1.x the two-month cycle will look as following:
12
12
- v1.x-RC.y - unstable version with cutting-edge features ready to test and feedback
13
13
- v1.x.y - stable version of the software **ready for production use**.
14
14
15
-
# How new features are merged
15
+
##How new features are merged
16
16
17
17
During RC features Pull Request with new features after feedback and acceptance are normally merged to `develop` branch.
18
-
After entering the Stabilization Phase we are tagging current develop branch, creating a `RC-x` (where `x` is a number of current version) branch from it and working on stabilization there.
18
+
After entering the Stabilization Phase we are tagging current develop branch, creating a `release/x` (where `x` is a number of current version) branch from it and working on stabilization there.
19
19
During the stabilization phase new features are merged to develop branch and will be merged on next `RC` phase.
20
20
21
+
## Release cycle flow
22
+
23
+
### 1. Development phase
24
+
25
+
The first phase of cycle we're mostly focusing on features and improvements. Branches in that phase should be created from actual `develop`, also PRs should be pointed to this branch. Changes merged to `develop` are available to test on https://test.storefrontcloud.io
At some point, when milestone for next minor versions is completed, we're creating new branch from `develop` called `release/vx.y` (example: `release/v1.9`).
32
+
After that new branch is tagged as first RC for version (example `v1.9.0-rc.1`). Then it's ready for testing by community.
33
+
During tests, feedback and stabilization there could be multiple Release Candidate versions on this branch. When improvement is made on this phase, then branch should be created from actual `release/vx.y` and should not contain features at this point - only improvements for current release.
34
+
After merging a set of bugfixes and improvements into `release/*` branch, it needs to be tagged as the next RC version and merged into the `develop` branch, to update it.
When RC version is stable, then release branch is merged into `master` and tagged as next stable version (example `v1.9.0`). After that currently merged release branch is deleted and starts new development phase. If some critical bug is discovered on current stable version, then new hotfix (for example `hotfix/v1.9.1`, following [Semantic Versioning rules](https://semver.org/)) branch should be created from actual `master`. After merging and testing hotfixes, this branch (like release branch before) is merged into `master` and tagged following [Semantic Versioning rules](https://semver.org/).
41
+
42
+

43
+
44
+
### Summary
45
+
46
+
Important thing to notice is that this releasing cycle ensures stable and reliable Storefront releases. Phases are also not blocking new features - you can develop new features on any phase, but it should be merged only to `develop` branch and go through whole cycle.
0 commit comments