From a31fcdcde3aed93df5df25071fbd29a6cab9d599 Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Fri, 10 Jun 2022 13:04:19 +0100 Subject: [PATCH] ;doc: RELEASING --- RELEASING.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index 9ad9a5e55..72686e069 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -98,9 +98,7 @@ Here are some definitions, useful eg when executing or automating release proced - Make things a little better each time through: simpler, more reliable, better documented, more automated, easier, faster, cheaper, higher quality. - Update [CHANGELOGS](CHANGELOGS.html) early and often, eg during/after a PR, to spread the work. - Make releases from a release branch, not from master. -- Before making binaries: - - Try to do all possible pre-release-tag steps. (Binaries will show their source's git hash in --version, and it should match the release tag.) - - Ensure the last commit does not begin with a semicolon. (So that the linux-x64-test workflow will generate a binary, in case it is needed.) +- Before making binaries: try to do all possible pre-release-tag steps. (Binaries' --version shows their git hash, and it should match the release tag.) - Before tagging: make binaries for all platforms, from the same commit. ### 1. Preview release