Additions to release guide and change to release note generation script #339
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.
While creating the 2023.08.0 release (#330) I could test the fantastic release guide by @GenevieveBuckley and found it super useful. Basically everything worked as described (there was some trouble during the release but unrelated to the release notes).
I didn't find that any particular step could be much simpler, but I completely agree that there's potential for automatization as discussed in #331.
One little problem that I encountered was that after copying the release notes generated by
generate_release_notes.py
toHISTORY.rst
and creating a release (candidate), twine complained about invalid restructured text. It turned out to be a too short title underline #334.So in this PR I'm
generate_release_notes.py
to produce rst compatible title underlines.Of course, this might not be very important or at least very transitory in the light of migrating to a more automated release process.