Skip to content

Commit fde224a

Browse files
committed
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.
1 parent 5165984 commit fde224a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/release-process.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ Generate the change log. As this is a huge amount of work to do manually, there
9898

9999
Generate list of authors:
100100

101-
git log --format='- %aN' v(current version, e.g. 0.20.0)..v(new version, e.g. 0.20.1) | sort -fiu
101+
git log --format='- %aN' v(current version, e.g. 24.0)..v(new version, e.g. 24.1) | sort -fiu
102102

103103
### Setup and perform Guix builds
104104

@@ -107,7 +107,7 @@ Checkout the Bitcoin Core version you'd like to build:
107107
```sh
108108
pushd ./bitcoin
109109
SIGNER='(your builder key, ie bluematt, sipa, etc)'
110-
VERSION='(new version without v-prefix, e.g. 0.20.0)'
110+
VERSION='(new version without v-prefix, e.g. 24.0)'
111111
git fetch origin "v${VERSION}"
112112
git checkout "v${VERSION}"
113113
popd

0 commit comments

Comments
 (0)