Kiu/VictoriaMetrics
Kiu/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-12-03 16:21:14 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

docs: fix step references in Release-Guide.md

Browse Source 
Signed-off-by: hagen1778 <roman@victoriametrics.com>
This commit is contained in:
hagen1778 2023-07-28 11:44:31 +02:00
parent 8f257889cc
commit b4fca28c29
No known key found for this signature in database
GPG Key ID: 3BF75F3741CA9640
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/Release-Guide.md
View File

@ -73,7 +73,7 @@ and make it merged. See example in this [commit](https://github.com/VictoriaMetr
* linux/ppc64le * linux/ppc64le
* linux/386 * linux/386
This step can be run manually with the command `make publish` from the needed git tag. This step can be run manually with the command `make publish` from the needed git tag.
1. Push the tags `v1.xx.y` and `v1.xx.y-cluster` created at step 2 to public GitHub repository at https://github.com/VictoriaMetrics/VictoriaMetrics. 1. Push the tags `v1.xx.y` and `v1.xx.y-cluster` created at step 8 to public GitHub repository at https://github.com/VictoriaMetrics/VictoriaMetrics.
Push the tags `v1.xx.y`, `v1.xx.y-cluster`, `v1.xx.y-enterprise` and `v1.xx.y-enterprise-cluster` to the corresponding Push the tags `v1.xx.y`, `v1.xx.y-cluster`, `v1.xx.y-enterprise` and `v1.xx.y-enterprise-cluster` to the corresponding
branches in private repository. branches in private repository.
**Important note:** do not push enterprise tags to public GitHub repository - they must be pushed only to private repository. **Important note:** do not push enterprise tags to public GitHub repository - they must be pushed only to private repository.
@ -81,7 +81,7 @@ and make it merged. See example in this [commit](https://github.com/VictoriaMetr
a) Create draft GitHub release with the name `TAG`. This step can be run manually a) Create draft GitHub release with the name `TAG`. This step can be run manually
with the command `TAG=v1.xx.y make github-create-release`. with the command `TAG=v1.xx.y make github-create-release`.
The release id is stored at `/tmp/vm-github-release` file. The release id is stored at `/tmp/vm-github-release` file.
b) Upload all the binaries and checksums created at step `3a` to that release. b) Upload all the binaries and checksums created at step `9a` to that release.
This step can be run manually with the command `make github-upload-assets`. This step can be run manually with the command `make github-upload-assets`.
It is expected that the needed release id is stored at `/tmp/vm-github-release` file, It is expected that the needed release id is stored at `/tmp/vm-github-release` file,
which must be created at the step `a`. which must be created at the step `a`.