aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarcoFalke <falke.marco@gmail.com>2018-05-30 08:38:26 -0400
committerMarcoFalke <falke.marco@gmail.com>2018-05-30 08:38:28 -0400
commit60f0358b4a1ee75bd02773e0eaa5dfd121389f25 (patch)
tree236e7d0297cf09bed6b717bf56473afdd4cbb11e
parentf8a29ca823fba7fc0eb63896ac4d3d5a0093a023 (diff)
parent83102388c00532602048f216e7d0a79eda81620c (diff)
downloadbitcoin-60f0358b4a1ee75bd02773e0eaa5dfd121389f25.tar.xz
Merge #13346: doc: update bitcoin-dot-org links in release-process.md
83102388c0 doc: update bitcoin-dot-org links in release-process.md (fanquake) Pull request description: Tree-SHA512: 664756780843e69a1b88eab573d451dfe4779281ad086406f35d641ca62b8369c7a8ccbd5eec2c81014da67233de5a8d8d77abcb65298d4783915cadbc102572
-rw-r--r--doc/release-process.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/release-process.md b/doc/release-process.md
index a988c74ba5..fb6f08750d 100644
--- a/doc/release-process.md
+++ b/doc/release-process.md
@@ -276,14 +276,14 @@ bitcoin.org (see below for bitcoin.org update instructions).
- Update bitcoin.org version
- First, check to see if the Bitcoin.org maintainers have prepared a
- release: https://github.com/bitcoin-dot-org/bitcoin.org/labels/Releases
+ release: https://github.com/bitcoin-dot-org/bitcoin.org/labels/Core
- 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-dot-org/bitcoin.org#release-notes
+ instructions: https://github.com/bitcoin-dot-org/bitcoin.org/blob/master/docs/adding-events-release-notes-and-alerts.md#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