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
DOC: Clarify merge policy #28046
DOC: Clarify merge policy #28046
Conversation
5266d93
to
1aa9722
Compare
fc19cfc
to
10cc1b5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mostly copy editing nits, I'm staying out of the review process for this.
10cc1b5
to
07906dd
Compare
ping |
It is docs, but I would like a second review on this. |
I think this needs a rebase to pick up #28094. |
Co-authored-by: Thomas A Caswell <tcaswell@gmail.com>
9bc06ca
to
11de885
Compare
Possibly tangential to this PR but matplotlib/doc/devel/pr_guide.rst Lines 204 to 205 in 11de885
I am not on any dev mailing list. Should I be? |
Couldn't hurt, it's https://mail.python.org/mailman/listinfo/matplotlib-devel which follow up would maybe be cross linking to the mailing list list
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is clear and very welcome.
Apologies for the tangent. Because of the context my brain went “wait, is there a mailing list for core devs?” |
Inspired by questions on some edge cases in the past (e.g. #28043 (review)).
One of the approvers should be @tacaswell .