joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-27 01:36:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

events_notes_alerts: Additional formatting fixes

Browse source
This commit is contained in:
Will Binns 2017-03-26 07:26:27 -06:00
parent be7f7242f5
commit 400c0c47bd
No known key found for this signature in database
GPG key ID: 302EBEAEEB74A404
1 changed files with 35 additions and 38 deletions
Download patch file Download diff file Expand all files Collapse all files

45
docs/adding-events-release-notes-and-alerts.md
View file

@ -107,10 +107,8 @@ is the particular version:
5. Open the failed Travis CI log. At the end, it will say something like:
```
ERROR:
Error: Could not retrieve
/bin/bitcoin-core-0.10.1/bitcoin-0.10.1-win64-setup.exe
Error: Could not retrieve
/bin/bitcoin-core-0.10.1/bitcoin-0.10.1-win32-setup.exe
Error: Could not retrieve /bin/bitcoin-core-0.10.1/bitcoin-0.10.1-win64-setup.exe
Error: Could not retrieve /bin/bitcoin-core-0.10.1/bitcoin-0.10.1-win32-setup.exe
[...]
```
6. Copy the errors from above into a text file and remove everything
@ -124,42 +122,41 @@ is the particular version:
8. Now open a pull request from the `bitcoin-core-<VERSION>` branch to
the `master` branch. We recommend that you use this title: "Releases:
Add Bitcoin Core &lt;VERSION>".
Add Bitcoin Core <VERSION>".
We recommend that you use the following text with any changes you
think are appropriate. **Note:** read all the way to the end of this
enumerated point before submitting your pull request.
```
This updates the download links to point to <VERSION> and adds the
<VERSION> release notes to the site. I'll keep it updated throughout
the RC cycle, but it can be merged by anyone with commit access
once <VERSION> final is released (see TODO lists below).
This updates the download links to point to <VERSION> and adds the <VERSION>
release notes to the site. I'll keep it updated throughout the RC cycle, but it
can be merged by anyone with commit access once <VERSION> final is released (see
TODO lists below).
CC: @laanwj
```
Essential TODO:
* [ ] Make sure the download links work. This is automatically checked
as part of the Travis CI build, so trigger a rebuild and, if it
passes, this should be safe to merge.
* [ ] Make sure the download links work. This is automatically checked as part
of the Travis CI build, so trigger a rebuild and, if it passes, this should be
safe to merge.
Optional TODO (may be done in commits after merge):
* [ ] Add the actual release date to the YAML header in
`_releases/0.10.1.md`
* [ ] Add the magnet URI to the YAML header in `_releases/0.10.1.md`
(brief instructions for creating the link are provided as comments in
that file)
* [ ] Add the actual release date to the YAML header in `_releases/0.10.1.md`
* [ ] Add the magnet URI to the YAML header in `_releases/0.10.1.md` (brief
instructions for creating the link are provided as comments in that file)
Expected URLs for the Bitcoin Core binaries:
Underneath the line 'Expected URLs', paste the URLs you retrieved
from Travis CI earlier.
```
Note that @laanwj is Wladimir J. van der Laan, who is usually
responsible for uploading the Bitcoin Core binaries. If someone
else is responsible for this release, CC them instead. If you don't
know who is responsible, ask in #bitcoin-dev on Freenode.
Underneath the line 'Expected URLs', paste the URLs you retrieved from Travis CI
earlier.
Note that @laanwj is Wladimir J. van der Laan, who is usually responsible for
uploading the Bitcoin Core binaries. If someone else is responsible for this
release, CC them instead. If you don't know who is responsible, ask in
#bitcoin-dev on Freenode.
9. After creating the pull request, use the Labels menu to assign it the
"Releases" label. This is important because it's what the Bitcoin