Skip to content

Update Release guide to current practices #25023

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jan 27, 2023

Conversation

QuLogic
Copy link
Member

@QuLogic QuLogic commented Jan 18, 2023

PR Summary

This updates the release guide to follow what I currently do. It also updates the helper scripts to clean up some minor whitespace issues that I always need to fix before committing.

Note that this is wrapped at 88, so may have to wait for PR #24893 to go in.

PR Checklist

Documentation and Tests

  • [n/a] Has pytest style unit tests (and pytest passes)
  • Documentation is sphinx and numpydoc compliant (the docs should build without error).
  • [n/a] New plotting related features are documented with examples.

Release Notes

  • [n/a] New features are marked with a .. versionadded:: directive in the docstring and documented in doc/users/next_whats_new/
  • [n/a] API changes are marked with a .. versionchanged:: directive in the docstring and documented in doc/api/next_api_changes/
  • [n/a] Release notes conform with instructions in next_whats_new/README.rst or next_api_changes/README.rst

Copy link
Member

@tacaswell tacaswell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

modulo waiting for the line length to be relaxed.

Comment on lines 44 to 46
API. Copy the current :file:`doc/users/github_stats.rst` to
:file:`doc/users/prev_whats_new/github_stats_{X}.{Y}.{Z}.rst`, changing the link target
at the top of the file, and removing the "Previous GitHub Stats" section at the end.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any chance this can be changed to a numbered list of steps? And the tenses here confuse me - does copying auto change things or do they need to be changed manually?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is an implied 'while' before the 'changing'.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can it be explicit?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure

@QuLogic QuLogic mentioned this pull request Jan 20, 2023
@QuLogic
Copy link
Member Author

QuLogic commented Jan 25, 2023

Note for later: add instruction to check spelling in GitHub stats, re #25084

This clears up the flake8 exception, and corrects the title and trailing
whitespace that I always need to clean up when committing the file.
Every run of the script adds an extra newline at the end.
@ksunden
Copy link
Member

ksunden commented Jan 26, 2023

Rebased and fixed the one remaining flake8 error (docstring in tools/github_stats.py)

Should be good to merge upon CI passing. (Was waiting for the line length bump)

@ksunden ksunden merged commit 84cc898 into matplotlib:main Jan 27, 2023
@QuLogic QuLogic deleted the release-guide branch February 21, 2023 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants