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/README.adoc
+2-7Lines changed: 2 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ To create release branches use the `create-release-branch.sh` script, called fro
56
56
----
57
57
58
58
- `-b <release>`: the release number (mandatory). This must be a semver-compatible value (i.e. without leading zeros) such as `23.1`, `23.10` etc. and will be used to create a branch with the name `release-<release>` e.g. `release-23.1`
59
-
- `-p`: push flag (optional, default is "false"). If provided, the created branches plus any changes made as part fo this process will be pushed to the origin.
59
+
- `-p`: push flag (optional, default is "false"). If provided, the created branches plus any changes made as part of this process will be pushed to the origin.
60
60
- `-c`: cleanup flag (optional, default is "false"). If provided, the repository folders will be torn down on completion.
61
61
- `-w`: where to create the branch. It can be "products", "operators", "both".
62
62
@@ -141,11 +141,6 @@ Some post release steps are performed with `release/post-release.sh` script, cal
141
141
- `-t <release-tag>`: the release tag (mandatory). This must be a semver-compatible value (i.e. major/minor/path, without leading zeros) such as `23.1.0`, `23.10.3` etc. and will be used to create a tag with the name
142
142
- `-p`: push flag (optional, default is "false"). If provided, the created commits and tags made as part of this process will be pushed to the origin.
143
143
144
-
[source]
145
-
----
146
-
./release/create-release-tag.sh -t 23.1.0 -p -c
147
-
----
148
-
149
144
#### What this script does
150
145
151
146
* checks that the release tag exists and that the all operator repositories have a clean working copy
@@ -206,7 +201,7 @@ To create release tags for bugfix/patch releases use the `create-bugfix-tag.sh`
- `-t <release-tag>`: the release tag (mandatory). This must be a semver-compatible value (i.e. major/minor/path, without leading zeros) such as `23.1.0`, `23.10.3` etc. and will be used to create a tag with the name
0 commit comments