From 2914a537dbad960839acf923f369d6b00733e4af Mon Sep 17 00:00:00 2001 From: Frederic Branczyk Date: Thu, 4 Jul 2019 15:18:39 +0200 Subject: [PATCH] RELEASE.md: Add procedure for when to publish docs Signed-off-by: Frederic Branczyk --- RELEASE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 3f86b86df..04fe497de 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -88,9 +88,9 @@ 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. -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. ### Pre-releases