diff options
author | Jon Atack <jon@atack.com> | 2019-03-15 14:23:40 +0100 |
---|---|---|
committer | Jon Atack <jon@atack.com> | 2019-05-10 20:35:30 +0200 |
commit | 96d32a7bc0902d615cae186dd5242fe9e10d2ff6 (patch) | |
tree | 19e41f03ca9019627deb2c486b48ca977901ab39 /doc/release-notes.md | |
parent | 14959753a424f04be118630f691ecab9b0df7e9e (diff) | |
download | bitcoin-96d32a7bc0902d615cae186dd5242fe9e10d2ff6.tar.xz |
[docs] Update release-process.md
- Create a release notes draft wiki for collaborative editing at https://github.com/bitcoin-core/bitcoin-devwiki/wiki as seen for releases 0.17.0 and 0.18.0.
- As per http://www.erisian.com.au/bitcoin-core-dev/log-2019-03-28.html#l-342, for the period during which the notes are being edited on the wiki, the version on the branch should be wiped and replaced with a link to the wiki which should be used for all announcements until final.
- Before final, remove the "Needs release note" label from relevant PRs/issues and merge the release notes from the wiki into the branch.
- Create a pinned meta-issue dedicated to testing the release candidate and communicate it in release announcements where useful. The former is done in practice (e.g. #15555, #14902) and the latter addresses the discussion here: https://x0f.org/web/statuses/101753569204220416.
- Adapt and merge the updates in https://github.com/bitcoin/bitcoin/pull/15692.
- Update the version numbers in all the examples.
- Reorganise the headers in the Branch Updates section.
Diffstat (limited to 'doc/release-notes.md')
0 files changed, 0 insertions, 0 deletions