Merge bitcoin/bitcoin#27484: doc: remove outdated version number usage from release-process

fde224a6610699a6a28cc27e299ac14cbf7e16ca doc: remove outdated version number usage from release-process (fanquake)

Pull request description:

  We no-longer use the leading `0.` version number, and having a mixture is both in the release-process examples is needlessly confusing.

ACKs for top commit:
  achow101:
    ACK fde224a6610699a6a28cc27e299ac14cbf7e16ca
  stickies-v:
    ACK fde224a6610699a6a28cc27e299ac14cbf7e16ca

Tree-SHA512: c6693b01741921f6870244243640fe857e024bb8581ce57b2d870abf20d257309b97af61fe464427e31a60cda78cf23c1012c6b6a2246250f3670c4b813417d9
This commit is contained in:
Andrew Chow 2023-04-18 09:56:20 -04:00
commit 2fa7344aa9
No known key found for this signature in database
GPG Key ID: 17565732E08E5E41

View File

@ -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