Commit 31b7b34d authored by intrigeri's avatar intrigeri

Make release notes writing instructions consistent with the implicit...

Make release notes writing instructions consistent with the implicit expectations of our release process doc (Closes: #16586)

Our release process assumes that tech writers will push the release notes
directly to the $WEBSITE_RELEASE_BRANCH (web/release-${TAG:?}) branch. But the
tech writers doc told them to do something else. Let's resolve this conflict.
parent 40aa8198
[[!meta title="Checklist for release notes"]]
- Create a branch based on the development branch for this release
- `web/nnnnn-x.y-release-notes`
- Fetch and checkout the `web/release-x.y` branch that was pushed
by the Release Manager
- Copy template from `contribute/how/documentation/release_notes/template.mdwn` to `news/version_x.y.mdwn`
- Replace placeholders in template
- Gather information about changes
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment