From 59e94dab4b5e0d7fce7c63fad3fc8361e48fe6ab Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Fri, 30 Jul 2021 21:47:22 +0930 Subject: [PATCH] doc/MAKING-RELEASES.md: advice on updating python package versions. Signed-off-by: Rusty Russell --- doc/MAKING-RELEASES.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/MAKING-RELEASES.md b/doc/MAKING-RELEASES.md index 1adb70f15..519c64d4d 100644 --- a/doc/MAKING-RELEASES.md +++ b/doc/MAKING-RELEASES.md @@ -30,7 +30,9 @@ Here's a checklist for the release process. 3. Create a new CHANGELOG.md heading to `vrc1`, and create a link at the bottom. Note that you should exactly copy the date and name format from a previous release, as the `build-release.sh` script relies on this. -4. Create a PR with the above. +4. Update the contrib/pyln package __version__ strings, but do not upload + it to pypi! +5. Create a PR with the above. ### Releasing -rc1 @@ -76,6 +78,8 @@ Here's a checklist for the release process. 10. Append the signatures into a file called `SHA256SUMS.asc`, verify with `gpg --verify SHA256SUMS.asc` and include the file in the draft release. +11. In each contrib/pyln-* directory, `make test-release` and if that succeeds, + `make prod-release` to upload to pypi.org. ### Performing the Release