aljaz/lightning
1
0
Fork 0
mirror of https://github.com/aljazceru/lightning.git synced 2025-12-22 08:34:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

doc/MAKING-RELEASES: clarifications based on previous release.

Browse Source 
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell
2019-01-11 15:25:54 +10:30
parent a2413f47e5
commit 75df22e9e2
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
doc/MAKING-RELEASES.md
View File

@@ -30,11 +30,12 @@ Here's a checklist for the release process.
[Unreleased] footnote URL from the previous version to the [Unreleased] footnote URL from the previous version to the
about-to-be-released version. about-to-be-released version.
2. Commit that, then `git tag -s v<VERSION> && git push --tags`. 2. Commit that, then `git tag -s v<VERSION> && git push --tags`.
3. Run `contrib/build-release.sh` to create the images and `SHA256SUMS`. 3. Run `tools/build-release.sh` to create the images, `SHA256SUMS` and
4. Upload the files resulting files the release notes to github and signatures into release/.
4. Upload the files resulting files to github and
save as a draft. save as a draft.
(https://github.com/ElementsProject/lightning/releases/) (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`. `gpg -sb --armor SHA256SUMS`.
6. Append the signatures into a file called `SHA256SUMS.asc`, verify 6. Append the signatures into a file called `SHA256SUMS.asc`, verify
with `gpg --verify SHA256SUMS.asc` and include the file in the draft with `gpg --verify SHA256SUMS.asc` and include the file in the draft