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
Copy file name to clipboardExpand all lines: RELEASE_GUIDELINES.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,8 +32,6 @@ reach out by [filing an issue](https://github.com/litmuschaos/litmus/issues).
32
32
33
33
- The chaos chart bundles are created by publishing the github releases for the [chaos-charts](https://github.com/litmuschaos/chaos-charts) repo. This is picked by the chaos [charthub](https://hub.litmuschaos.io) for user download.
34
34
35
-
- Tracking of releases is done on Github [project board](https://github.com/litmuschaos/litmus/projects)
36
-
37
35
- The release flow consists of the following steps:
38
36
39
37
- Sprint Planning based on backlogs & feature requests from the community
@@ -56,16 +54,16 @@ considered "pre-releases".
56
54
57
55
### Major and Minor Releases
58
56
59
-
Major and minor releases of LitmusChaos will be made from main. Releases of
57
+
Major and minor releases of LitmusChaos will be made from master. Releases of
60
58
LitmusChaos will be marked with GPG signed tags and announced at
61
-
https://github.com/LitmusChaos/LitmusChaos/releases. The tag will be of the
62
-
format `v<major>.<minor>.<patch>` and should be made with the command `git tag
63
-
-s v<major>.<minor>.<patch>`.
59
+
https://github.com/litmuschaos/litmus/releases. The tag will be of the
60
+
format `<major>.<minor>.<patch>` and should be made with the command `git tag
61
+
-s <major>.<minor>.<patch>`.
64
62
65
63
After a minor release, a branch will be created, with the format
66
-
`release/<major>.<minor>` from the minor tag. All further patch releases will
67
-
be done from that branch. For example, once we release `v1.0.0`, a branch
68
-
`release/1.0` will be created from that tag. All future patch releases will be
64
+
`release-<major>.<minor>.x` from the minor tag. All further patch releases will
65
+
be done from that branch. For example, once we release `1.0.0`, a branch
66
+
`release-1.0.x` will be created from that tag. All future patch releases will be
0 commit comments