Skip to content

Doc merge up api whats new #10414

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 9 commits into from
Feb 12, 2018

Conversation

tacaswell
Copy link
Member

PR Summary

PR Checklist

  • Has Pytest style unit tests
  • Code is PEP 8 compliant
  • New features are documented, with examples if plot related
  • Documentation is sphinx and numpydoc compliant
  • Added an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)
  • Documented in doc/api/api_changes.rst if API changed in a backward-incompatible way

@tacaswell tacaswell added this to the v2.2 milestone Feb 11, 2018
@tacaswell tacaswell added Documentation Release critical For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions. labels Feb 11, 2018
@tacaswell tacaswell force-pushed the doc_merge_up_api_whats_new branch from 4f7f1f3 to 9b34789 Compare February 11, 2018 06:44
@tacaswell tacaswell force-pushed the doc_merge_up_api_whats_new branch from 9b34789 to 1410c1f Compare February 12, 2018 02:04
@tacaswell
Copy link
Member Author

I intend to self-merge this once the CI passes.

@tacaswell tacaswell merged commit b541a8a into matplotlib:master Feb 12, 2018
@tacaswell tacaswell deleted the doc_merge_up_api_whats_new branch February 12, 2018 03:30
@QuLogic QuLogic modified the milestones: needs sorting, v2.2.0 Feb 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Release critical For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants