Skip to content

Commit

Permalink
Merge pull request bitcoin#5961
Browse files Browse the repository at this point in the history
bf1cc80 Docs: Use new Bitcoin.org download URLs (David A. Harding)
  • Loading branch information
laanwj committed Apr 3, 2015
2 parents 9e1cc16 + bf1cc80 commit 24e4899
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 7 deletions.
4 changes: 2 additions & 2 deletions doc/release-notes.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
Bitcoin Core version 0.10.1 is now available from:

https://bitcoin.org/bin/0.10.1/
<https://bitcoin.org/bin/bitcoin-core-0.10.1/>

This is a new minor version release, bringing bug fixes and translation
updates. If you are using 0.10.0, it is recommended to upgrade to this
version.

Please report bugs using the issue tracker at github:

https://github.com/bitcoin/bitcoin/issues
<https://github.com/bitcoin/bitcoin/issues>

Upgrading and downgrading
=========================
Expand Down
17 changes: 12 additions & 5 deletions doc/release-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -132,15 +132,22 @@ rm SHA256SUMS
(the digest algorithm is forced to sha256 to avoid confusion of the `Hash:` header that GPG adds with the SHA256 used for the files)

- 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

- Make a pull request to add a file named `YYYY-MM-DD-vX.Y.Z.md` with the release notes
to https://github.com/bitcoin/bitcoin.org/tree/master/_releases
([Example for 0.9.2.1](https://raw.githubusercontent.com/bitcoin/bitcoin.org/master/_releases/2014-06-19-v0.9.2.1.md)).
- First, check to see if the Bitcoin.org maintainers have prepared a
release: https://github.com/bitcoin/bitcoin.org/labels/Releases

- After the pull request is merged, the website will automatically show the newest version, as well
as update the OS download links. Ping Saivann in case anything goes wrong
- If they have, it will have previously failed their Travis CI
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:

Expand Down

0 comments on commit 24e4899

Please sign in to comment.