Docs: Use new Bitcoin.org download URLs

This commit is contained in:
David A. Harding 2015-04-03 07:51:31 +02:00 committed by Wladimir J. van der Laan
parent 15facb4aca
commit 2dc679d22f
No known key found for this signature in database
GPG Key ID: 74810B012346C9A6
1 changed files with 12 additions and 5 deletions

View File

@ -133,15 +133,22 @@ rm SHA256SUMS
Note: check that SHA256SUMS itself doesn't end up in SHA256SUMS, which is a spurious/nonsensical entry. Note: check that SHA256SUMS itself doesn't end up in SHA256SUMS, which is a spurious/nonsensical entry.
- Upload zips and installers, as well as `SHA256SUMS.asc` from last step, to the bitcoin.org server - Upload zips and installers, as well as `SHA256SUMS.asc` from last step, to the bitcoin.org server
into `/var/www/bin/bitcoin-core-${VERSION}`
- Update bitcoin.org version - Update bitcoin.org version
- Make a pull request to add a file named `YYYY-MM-DD-vX.Y.Z.md` with the release notes - First, check to see if the Bitcoin.org maintainers have prepared a
to https://github.com/bitcoin/bitcoin.org/tree/master/_releases release: https://github.com/bitcoin/bitcoin.org/labels/Releases
([Example for 0.9.2.1](https://raw.githubusercontent.com/bitcoin/bitcoin.org/master/_releases/2014-06-19-v0.9.2.1.md)).
- After the pull request is merged, the website will automatically show the newest version, as well - If they have, it will have previously failed their Travis CI
as update the OS download links. Ping Saivann in case anything goes wrong checks because the final release files weren't uploaded.
Trigger a Travis CI rebuild---if it passes, merge.
- If they have not prepared a release, follow the Bitcoin.org release
instructions: https://github.com/bitcoin/bitcoin.org#release-notes
- After the pull request is merged, the website will automatically show the newest version within 15 minutes, as well
as update the OS download links. Ping @saivann/@harding (saivann/harding on Freenode) in case anything goes wrong
- Announce the release: - Announce the release: