neobytes-project/neobytes
neobytes-project/neobytes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Docs: Use new Bitcoin.org download URLs

Browse Source 
To give the torrents (which use web seeds) better names, we updated the
URL scheme on bitcoin.org/bin. This updates the release notes and
release doc accordingly, plus updates some other details based on recent
changes to the site.

[skip ci]
This commit is contained in:
David A. Harding 2015-04-02 10:34:26 -04:00
parent 9e1cc16296
commit bf1cc80372
No known key found for this signature in database
GPG Key ID: 4B29C30FF29EC4B7
2 changed files with 14 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/release-notes.md
View File

@ -1,6 +1,6 @@
Bitcoin Core version 0.10.1 is now available from: 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 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 updates. If you are using 0.10.0, it is recommended to upgrade to this
@ -8,7 +8,7 @@ version.
Please report bugs using the issue tracker at github: Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues <https://github.com/bitcoin/bitcoin/issues>
Upgrading and downgrading Upgrading and downgrading
========================= =========================

17
doc/release-process.md
View File

@ -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) (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 - 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: