Adapt the release guide to the new release notes structure #20498
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
46de782 to
043e722
Compare
jklymak
approved these changes
Jul 4, 2021
|
@QuLogic, plus or minus the rebase, does this look right/useful to you? |
|
@timhoffm feel free to merge after rebase... |
043e722 to
49f8a99
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Summary
This reflects the restructuring in #20132. It should make handling "Whats new" and "API changes" simpler because one doesn't have to touch the respective
next_*.rstanymore. A release simply gets two new pageswhats_new_X.Y.Z.rstandapi_changes_X.Y.Z.rst, which are added to the TOC inrelease_notes.rst.Ping in particular @QuLogic since you will have to use this.