doc: Mention wiki release notes draft in release-process #15692
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Is this done in #15607 ? |
Contributor
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
Member
|
Closing this, as a similar change is now in #15607. |
jonatack
added a commit
to jonatack/bitcoin
that referenced
this pull request
May 10, 2019
- 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. bitcoin#15555, bitcoin#14902) and the latter addresses the discussion here: https://x0f.org/web/statuses/101753569204220416. - Adapt and merge the updates in bitcoin#15692. - Update the version numbers in all the examples. - Reorganise the headers in the Branch Updates section.
jonatack
added a commit
to jonatack/bitcoin
that referenced
this pull request
May 10, 2019
- Write an introduction explaining how to use the release-notes.md template. - Adapt and merge the updates in bitcoin#15692.
maflcko
pushed a commit
that referenced
this pull request
May 10, 2019
bd63c1e [docs] Update release-notes.md (Jon Atack) 96d32a7 [docs] Update release-process.md (Jon Atack) Pull request description: Updates to `release-notes.md`: - Write an introduction explaining how to use `release-notes.md` as a template for the release notes draft wiki for collaborative editing at https://github.com/bitcoin-core/bitcoin-devwiki/wiki, as seen for the 0.17.0 and 0.18.0 releases. Updates to `release-process.md`: - Create a release notes draft wiki at https://github.com/bitcoin-core/bitcoin-devwiki/wiki. - As per http://www.erisian.com.au/bitcoin-core-dev/log-2019-03-28.html#l-342, for the period during which the release 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 yesterday: https://x0f.org/web/statuses/101753569204220416. - Reorganise the headers in the Branch Updates section. - Update the version numbers in the examples. - Adapt and merge in the updates in #15692. ACKs for commit bd63c1: Tree-SHA512: a436d6d0971bf00f081d4e2660c3b37a0f96913236c33934453387d63c11556a80e428b110f5629f07a6aa98e627f86c799d10c3f40e9f0c27b22275e04f6fa8
sidhujag
pushed a commit
to syscoin/syscoin
that referenced
this pull request
May 10, 2019
- 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. bitcoin#15555, bitcoin#14902) and the latter addresses the discussion here: https://x0f.org/web/statuses/101753569204220416. - Adapt and merge the updates in bitcoin#15692. - Update the version numbers in all the examples. - Reorganise the headers in the Branch Updates section.
sidhujag
pushed a commit
to syscoin/syscoin
that referenced
this pull request
May 10, 2019
- Write an introduction explaining how to use the release-notes.md template. - Adapt and merge the updates in bitcoin#15692.
HashUnlimited
pushed a commit
to HashUnlimited/chaincoin
that referenced
this pull request
Aug 30, 2019
- 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. bitcoin#15555, bitcoin#14902) and the latter addresses the discussion here: https://x0f.org/web/statuses/101753569204220416. - Adapt and merge the updates in bitcoin#15692. - Update the version numbers in all the examples. - Reorganise the headers in the Branch Updates section.
HashUnlimited
pushed a commit
to HashUnlimited/chaincoin
that referenced
this pull request
Aug 30, 2019
- Write an introduction explaining how to use the release-notes.md template. - Adapt and merge the updates in bitcoin#15692.
barrystyle
pushed a commit
to zentoshi/zentoshi
that referenced
this pull request
Nov 11, 2019
- 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 bitcoin/bitcoin#15692. - Update the version numbers in all the examples. - Reorganise the headers in the Branch Updates section.
barrystyle
pushed a commit
to zentoshi/zentoshi
that referenced
this pull request
Nov 11, 2019
- Write an introduction explaining how to use the release-notes.md template. - Adapt and merge the updates in bitcoin/bitcoin#15692.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.