RELEASE.md: Add command to run benchmark on release candidates

Signed-off-by: Frederic Branczyk <fbranczyk@gmail.com>
5 years ago · ac7b0ae4e6
parent 2914a537db
commit ac7b0ae4e6
1 changed files with 1 additions and 0 deletions
--- 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.