diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2022-03-16 14:11:26 +0100 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2022-03-17 14:15:07 +0100 |
| commit | fa4943e8df2e1048a5030f1d93776ca2b9da7b8a (patch) | |
| tree | b1ed9c6a56eef28f1c705cd2f2fd44b63d5b4da9 /doc/release-process.md | |
| parent | bf2c0fb2a26432762bf98e19a98e252b7bdd7d30 (diff) | |
| download | bitcoin-fa4943e8df2e1048a5030f1d93776ca2b9da7b8a.tar.xz | |
doc: Add template for empty release notes
Diffstat (limited to 'doc/release-process.md')
| -rw-r--r-- | doc/release-process.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/release-process.md b/doc/release-process.md index 5a74f72b6e..6a2a849c00 100644 --- a/doc/release-process.md +++ b/doc/release-process.md @@ -47,13 +47,15 @@ Release Process #### After branch-off (on the major release branch) - Update the versions. +- Create the draft, named "*version* Release Notes Draft", as a [collaborative wiki](https://github.com/bitcoin-core/bitcoin-devwiki/wiki/_new). +- Clear the release notes: `cp doc/release-notes-empty-template.md doc/release-notes.md` - Create a pinned meta-issue for testing the release candidate (see [this issue](https://github.com/bitcoin/bitcoin/issues/17079) for an example) and provide a link to it in the release announcements where useful. - Translations on Transifex - Change the auto-update URL for the new major version's resource away from `master` and to the branch, e.g. `https://raw.githubusercontent.com/bitcoin/bitcoin/<branch>/src/qt/locale/bitcoin_en.xlf`. Do not forget this or it will keep tracking the translations on master instead, drifting away from the specific major release. #### Before final release -- Merge the release notes from the wiki into the branch. +- Merge the release notes from [the wiki](https://github.com/bitcoin-core/bitcoin-devwiki/wiki/) into the branch. - Ensure the "Needs release note" label is removed from all relevant pull requests and issues. #### Tagging a release (candidate) |