Skip to content

Backport PR #12394 on branch v3.0.x (DOC: fix CL tutorial to give same output from saved file and example) #12412

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

Conversation

meeseeksmachine
Copy link
Contributor

Backport PR #12394: DOC: fix CL tutorial to give same output from saved file and example

@lumberbot-app lumberbot-app bot added this to the v3.0.0-doc milestone Oct 5, 2018
@jklymak
Copy link
Member

jklymak commented Oct 5, 2018

I'll close this - I don't think it is urgent need of backporting. Sorry - I find the 3.0.0-doc branch confusing so I probably mis-milestoned...

@jklymak jklymak closed this Oct 5, 2018
@ImportanceOfBeingErnest
Copy link
Member

Oh yes, confusing indeed. I thought everything that concerns the current documentation should go in that branch, such that the online docs can be updated more frequently than library releases?

@jklymak
Copy link
Member

jklymak commented Oct 5, 2018

I guess thats correct.... Sorry I hadn't realized you'd milestoned it. We can re-open. Doesn't hurt anything...

@jklymak jklymak reopened this Oct 5, 2018
@ImportanceOfBeingErnest
Copy link
Member

Oh, but now I'm even more confused. This is a backport PR for the v3.0.x branch, not the v3.0.0-doc branch. But mister meee added this PR to the v3.0.0-doc milestone as well, in addition to creating #12413.

I think it would be helpful if someone could extend the branches and backports section a bit concerning this topic.

@jklymak
Copy link
Member

jklymak commented Oct 5, 2018

That’s what confused me. But I think it’s right. We want future releases to have 3.0.0 changes.

@jklymak jklymak merged commit faae77e into matplotlib:v3.0.x Oct 5, 2018
@QuLogic QuLogic modified the milestones: v3.0.0-doc, v3.0.x Oct 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants