aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorfanquake <fanquake@gmail.com>2023-04-18 12:36:19 +0100
committerfanquake <fanquake@gmail.com>2023-04-18 12:36:19 +0100
commitfde224a6610699a6a28cc27e299ac14cbf7e16ca (patch)
tree66867a9821cf7e58ddd05af6598ea0398046788d /doc
parent5165984afcc035fd4a94c7b6b70a016097c7e673 (diff)
downloadbitcoin-fde224a6610699a6a28cc27e299ac14cbf7e16ca.tar.xz
doc: remove outdated version number usage from release-process
We no-longer use the leading 0. version number, and having a mixture is both in the release-process examples is needlessly confusing.
Diffstat (limited to 'doc')
-rw-r--r--doc/release-process.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/release-process.md b/doc/release-process.md
index f1fd72f8ac..cd1b38059e 100644
--- a/doc/release-process.md
+++ b/doc/release-process.md
@@ -98,7 +98,7 @@ Generate the change log. As this is a huge amount of work to do manually, there
Generate list of authors:
- git log --format='- %aN' v(current version, e.g. 0.20.0)..v(new version, e.g. 0.20.1) | sort -fiu
+ git log --format='- %aN' v(current version, e.g. 24.0)..v(new version, e.g. 24.1) | sort -fiu
### Setup and perform Guix builds
@@ -107,7 +107,7 @@ Checkout the Bitcoin Core version you'd like to build:
```sh
pushd ./bitcoin
SIGNER='(your builder key, ie bluematt, sipa, etc)'
-VERSION='(new version without v-prefix, e.g. 0.20.0)'
+VERSION='(new version without v-prefix, e.g. 24.0)'
git fetch origin "v${VERSION}"
git checkout "v${VERSION}"
popd