Skip to content

Commit d1c2ed8

Browse files
author
MarcoFalke
committed
Merge #15821: doc: Remove upgrade note in release notes from EOL versions
fa346fe doc: Remove upgrade note in release notes from EOL versions (MarcoFalke) Pull request description: Remove the bloat on how to upgrade from version that are EOL ACKs for commit fa346f: fanquake: re-utACK fa346fe Tree-SHA512: 201e8594ef13523a04c7546995462d15d19bb80dbbca8d5cbf439cfd04af290ffd44f00a2e52ca1b88f1f17bf8bb09e9c4384cf1183d744d5301633e9b9507c0
2 parents 2d4f70c + fa346fe commit d1c2ed8

File tree

1 file changed

+3
-8
lines changed

1 file changed

+3
-8
lines changed

doc/release-notes.md

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -24,14 +24,9 @@ shut down (which might take a few minutes for older versions), then run the
2424
installer (on Windows) or just copy over `/Applications/Bitcoin-Qt` (on Mac)
2525
or `bitcoind`/`bitcoin-qt` (on Linux).
2626

27-
The first time you run version 0.15.0, your chainstate database will be converted to a
28-
new format, which will take anywhere from a few minutes to half an hour,
29-
depending on the speed of your machine.
30-
31-
Note that the block database format also changed in version 0.8.0 and there is no
32-
automatic upgrade code from before version 0.8 to version 0.15.0. Upgrading
33-
directly from 0.7.x and earlier without redownloading the blockchain is not supported.
34-
However, as usual, old wallet versions are still supported.
27+
Upgrading directly from a version of Bitcoin Core that has reached its EOL is
28+
possible, but might take some time if the datadir needs to be migrated. Old
29+
wallet versions of Bitcoin Core are generally supported.
3530

3631
Downgrading warning
3732
-------------------

0 commit comments

Comments
 (0)