From ac7b0ae4e6a7e9e5c9eae90f16d393a78a1fea77 Mon Sep 17 00:00:00 2001 From: Frederic Branczyk Date: Thu, 4 Jul 2019 15:47:32 +0200 Subject: [PATCH] RELEASE.md: Add command to run benchmark on release candidates Signed-off-by: Frederic Branczyk --- RELEASE.md | 1 + 1 file changed, 1 insertion(+) diff --git a/RELEASE.md b/RELEASE.md index 04fe497de..3c1917ba8 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -99,4 +99,5 @@ The following changes to the above procedures apply: * In line with [Semantic Versioning](https://semver.org/), append something like `-rc.0` to the version (with the corresponding changes to the tag name, the release name etc.). * Tick the _This is a pre-release_ box when drafting the release in the Github UI. * Still update `CHANGELOG.md`, but when you cut the final release later, merge all the changes from the pre-releases into the one final update. +* Run the benchmark for 3 days using the `/benchmark x.y.z` command, `x.y.z` being the latest stable patch release of the previous minor release series.