Skip to content
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

Merged
merged 2 commits into from May 9, 2024
Merged

Conversation

timhoffm
Copy link
Member

@timhoffm timhoffm commented Apr 8, 2024

Inspired by questions on some edge cases in the past (e.g. #28043 (review)).

One of the approvers should be @tacaswell .

@timhoffm timhoffm requested a review from tacaswell April 8, 2024 12:06
@github-actions github-actions bot added the Documentation: devdocs files in doc/devel label Apr 8, 2024
@timhoffm timhoffm added this to the v3.10.0 milestone Apr 8, 2024
@timhoffm timhoffm force-pushed the doc-clarify-merge-policy branch 2 times, most recently from fc19cfc to 10cc1b5 Compare April 8, 2024 12:22
Copy link
Member

@story645 story645 left a 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.

doc/devel/pr_guide.rst Outdated Show resolved Hide resolved
doc/devel/pr_guide.rst Outdated Show resolved Hide resolved
doc/devel/pr_guide.rst Outdated Show resolved Hide resolved
doc/devel/pr_guide.rst Outdated Show resolved Hide resolved
doc/devel/pr_guide.rst Outdated Show resolved Hide resolved
doc/devel/pr_guide.rst Outdated Show resolved Hide resolved
@timhoffm
Copy link
Member Author

timhoffm commented May 5, 2024

ping

@tacaswell
Copy link
Member

It is docs, but I would like a second review on this.

@rcomer
Copy link
Member

rcomer commented May 6, 2024

I think this needs a rebase to pick up #28094.

timhoffm and others added 2 commits May 6, 2024 21:38
Co-authored-by: Thomas A Caswell <tcaswell@gmail.com>
@rcomer
Copy link
Member

rcomer commented May 8, 2024

Possibly tangential to this PR but

to do so, they should ping all core devs both on GitHub and on the dev
mailing list, and label the PR with the "Merge with single review?" label.

I am not on any dev mailing list. Should I be?

@story645
Copy link
Member

story645 commented May 8, 2024

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 :ref:`mailing-lists`

Copy link
Member

@rcomer rcomer left a 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.

@rcomer
Copy link
Member

rcomer commented May 9, 2024

Apologies for the tangent. Because of the context my brain went “wait, is there a mailing list for core devs?”

@rcomer rcomer merged commit d67f08e into matplotlib:main May 9, 2024
22 checks passed
@timhoffm timhoffm deleted the doc-clarify-merge-policy branch May 9, 2024 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation: devdocs files in doc/devel
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants