Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Rename next_api_changes to api_changes_3.x (whatever number makes sense) #16588

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.

Sign up for GitHub

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

Jump to bottom
Closed
anntzer opened this issue Feb 27, 2020 · 0 comments · Fixed by #17021
Closed

Rename next_api_changes to api_changes_3.x (whatever number makes sense) #16588

anntzer opened this issue Feb 27, 2020 · 0 comments · Fixed by #17021
Labels
Documentation
Milestone
v3.3.0

Comments

@anntzer
Copy link
Contributor

anntzer commented Feb 27, 2020

Putting an actual version number on the next_api_changes directory may help avoiding notes going to the wrong file during long RC periods where it's not so obvious whether next_api_changes refers to the currently rc'd release, or the next one. See e.g. #16457 (comment).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Documentation
Projects
None yet
Milestone
v3.3.0
Development

Successfully merging a pull request may close this issue.

File name made more understandable SidharthBansal/matplotlib
2 participants
@QuLogic @anntzer