From 75df22e9e24fa94de7fd6232bed4577b219c93f9 Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Fri, 11 Jan 2019 15:25:54 +1030 Subject: [PATCH] doc/MAKING-RELEASES: clarifications based on previous release. Signed-off-by: Rusty Russell --- doc/MAKING-RELEASES.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/MAKING-RELEASES.md b/doc/MAKING-RELEASES.md index 29ef039cb..24f5d9930 100644 --- a/doc/MAKING-RELEASES.md +++ b/doc/MAKING-RELEASES.md @@ -30,11 +30,12 @@ Here's a checklist for the release process. [Unreleased] footnote URL from the previous version to the about-to-be-released version. 2. Commit that, then `git tag -s v && git push --tags`. -3. Run `contrib/build-release.sh` to create the images and `SHA256SUMS`. -4. Upload the files resulting files the release notes to github and +3. Run `tools/build-release.sh` to create the images, `SHA256SUMS` and + signatures into release/. +4. Upload the files resulting files to github and save as a draft. (https://github.com/ElementsProject/lightning/releases/) -5. Ping the rest of the team to check the SHA256SUMS file and then +5. Ping the rest of the team to check the SHA256SUMS file and have them `gpg -sb --armor SHA256SUMS`. 6. Append the signatures into a file called `SHA256SUMS.asc`, verify with `gpg --verify SHA256SUMS.asc` and include the file in the draft