mirror of
https://github.com/prometheus/prometheus
synced 2024-12-25 07:52:28 +00:00
Simplify tagging section to reduce chance of misinterpreting what the
tag should be. Signed-off-by: Callum Styan <callumstyan@gmail.com>
This commit is contained in:
parent
6ad7ec50f7
commit
53aa2541e5
@ -98,9 +98,7 @@ Entries in the `CHANGELOG.md` are meant to be in this order:
|
|||||||
|
|
||||||
### 2. Draft the new release
|
### 2. Draft the new release
|
||||||
|
|
||||||
Tag the new release with a tag named `v<major>.<minor>.<patch>`, e.g. `v2.1.3`. Note the `v` prefix.
|
Tag the new release via the following commands:
|
||||||
|
|
||||||
You can do the tagging on the commandline:
|
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
$ tag=$(< VERSION)
|
$ tag=$(< VERSION)
|
||||||
@ -123,6 +121,4 @@ If the release has happened in the latest release branch, merge the changes into
|
|||||||
|
|
||||||
To update the docs, a PR needs to be created to `prometheus/docs`. See [this PR](https://github.com/prometheus/docs/pull/952/files) for inspiration (note: only actually merge this for final releases, not for pre-releases like a release candidate).
|
To update the docs, a PR needs to be created to `prometheus/docs`. See [this PR](https://github.com/prometheus/docs/pull/952/files) for inspiration (note: only actually merge this for final releases, not for pre-releases like a release candidate).
|
||||||
|
|
||||||
Once the binaries have been uploaded, announce the release on `prometheus-announce@googlegroups.com`. (Please do not use `prometheus-users@googlegroups.com` for announcements anymore.) Check out previous announcement mails for inspiration.
|
Once the binaries have been uploaded, announce the release on `prometheus-announce@googlegroups.com`. (Please do not use `prometheus-users@googlegroups.com` for announcements anymore.) Check out previous announcement mails for inspiration.
|
||||||
|
|
||||||
Finally, open a PR in the docs repo to
|
|
Loading…
Reference in New Issue
Block a user