Skip to content

Commit

Permalink
doc: remove outdated version number usage from release-process
Browse files Browse the repository at this point in the history
We no-longer use the leading 0. version number, and having a mixture is
both in the release-process examples is needlessly confusing.
  • Loading branch information
fanquake committed Apr 18, 2023
1 parent 5165984 commit fde224a
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions doc/release-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand All @@ -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
Expand Down

0 comments on commit fde224a

Please sign in to comment.