github
/
prometheus
mirror of https://github.com/prometheus/prometheus
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

RELEASE.md: Add procedure for when to publish docs

Browse Source 
Signed-off-by: Frederic Branczyk <fbranczyk@gmail.com>
pull/5736/head
Frederic Branczyk 5 years ago
parent 5d84b76b81
commit 2914a537db
No known key found for this signature in database
GPG Key ID: 7741A52782A90069
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File

2
RELEASE.md
Unescape View File

@ -88,7 +88,7 @@ Now all you can do is to wait for tarballs to be uploaded to the Github release
If the release has happened in the latest release branch, merge the changes into master. If the release has happened in the latest release branch, merge the changes into master.
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. 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.

Write Preview
Loading…
Cancel
Save