Repository navigation
Moving release notes to the release notes section - #2727
Open
john-science wants to merge 3 commits into
Open
john-science wants to merge 3 commits into
john-science wants to merge 3 commits into
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
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.
What is the change? Why is it being made?
We are required to have an active SCR section, to fill our need for a "rolling SCR" section, to be kept updated with every commit.
But we had an empty Release Notes section which pointed to some odd links to the SCR subsections. But those subsections are not really PART of the current SCR.
Anyway, I think this new version is a lot more clear.
SCR Information
Change Type: docs
One-Sentence Rationale: The release and SCR sections were mixed, and that was less clear.
One-line Impact on Requirements: NA
Checklist
docfolder.pyproject.toml.