aboutsummaryrefslogtreecommitdiff
path: root/doc/release-process.md
diff options
context:
space:
mode:
authorMarcoFalke <falke.marco@gmail.com>2021-10-20 13:26:51 +0200
committerMarcoFalke <falke.marco@gmail.com>2021-10-20 18:45:03 +0200
commitfa38d98aa98bcf34b5b59ff894bbb5da67355b29 (patch)
tree3c4681367e059215c0ff0bb2ec609b08c3b8a07e /doc/release-process.md
parentf9ad4d51e3dbb84036762f5a9e0c6d712e49d1be (diff)
doc: Add note on deleting past-EOL release branches
Diffstat (limited to 'doc/release-process.md')
-rw-r--r--doc/release-process.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/release-process.md b/doc/release-process.md
index 6a5202d0f9..14567d4f15 100644
--- a/doc/release-process.md
+++ b/doc/release-process.md
@@ -60,7 +60,7 @@ Release Process
To tag the version (or release candidate) in git, use the `make-tag.py` script from [bitcoin-maintainer-tools](https://github.com/bitcoin-core/bitcoin-maintainer-tools). From the root of the repository run:
- ../bitcoin-maintainer-tools/make-tag.py v(new version, e.g. 0.20.0)
+ ../bitcoin-maintainer-tools/make-tag.py v(new version, e.g. 23.0)
This will perform a few last-minute consistency checks in the build system files, and if they pass, create a signed tag.
@@ -253,6 +253,10 @@ cat "$VERSION"/*/all.SHA256SUMS.asc > SHA256SUMS.asc
- bitcoincore.org maintained versions update:
[table](https://github.com/bitcoin-core/bitcoincore.org/commits/master/_includes/posts/maintenance-table.md)
+ - Delete post-EOL [release branches](https://github.com/bitcoin/bitcoin/branches/all) and create a tag `v${branch_name}-final`.
+
+ - Delete ["Needs backport" labels](https://github.com/bitcoin/bitcoin/labels?q=backport) for non-existing branches.
+
- bitcoincore.org RPC documentation update
- Install [golang](https://golang.org/doc/install)