8000 Fix inverted expected/found FreeType version warning. by QuLogic · Pull Request #7881 · matplotlib/matplotlib · GitHub
[go: up one dir, main page]

Skip to content

Fix inverted expected/found FreeType version warning. #7881

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 1 commit into from
Jan 23, 2017

Conversation

QuLogic
Copy link
Member
@QuLogic QuLogic commented Jan 20, 2017

I've always been confused by this message, and it turns out it's backwards.

@QuLogic QuLogic added this to the 2.0.1 (next bug fix release) milestone Jan 20, 2017
Copy link
Member
@NelleV NelleV left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The patch looks fine, but I would not tag this for 2.0.1
I am once again concerned about how many pull requests are being tagged for 2.0.1 and are backported. We have more pull request tagged 2.0.1 than we have for 2.1. At this point, it'll be easier to do the next minor release than the 2.0.1 micro release.

@NelleV NelleV changed the title Fix inverted expected/found FreeType version warning. [MRG+1] Fix inverted expected/found FreeType version warning. Jan 20, 2017
@dopplershift
Copy link
Contributor

On this particular one, it's targetted to the right branch, so no backport for the 2.0.1 release--just a merge to master at some point. It's also clearly a bug fix (not super critical, but almost zero risk). I'm not sure what's wrong with putting this in the next release.

@NelleV
Copy link
Member
NelleV commented Jan 20, 2017

@dopplershift My concern with this state of mind is that we backport everything.

@dopplershift
Copy link
Contributor

Ah. Might want to pick that battle on something that's more arguably out of bounds. 😁

@NelleV
Copy link
Member
NelleV commented Jan 20, 2017

@dopplershift I think only major bugs should be backported: this isn't a major bug.

@dopplershift
Copy link
Contributor

My take is if it's a bug, and the fix is ready, it goes in, with one proviso: The lines in question have to have tests to ensure that it didn't accidentally break something. It doesn't have to be a new test (a test for this specific change would just be silly), but the test suite should be executing any lines that changed.

I have no idea if this change was run by the tests or not.

@QuLogic
Copy link
Member Author
QuLogic commented Jan 21, 2017

I have no idea if this change was run by the tests or not.

Unfortunately not; all tests are run with the builtin freetype version, so this warning will never be triggered on CI. Locally, however, I never build with local_freetype=True, so I'm fairly certain that the warning gets the message backwards.

@dopplershift
Copy link
Contributor

Less concerned about whether they're backwards (I trust you) and more about making sure there's a test somehow that makes sure there's not an unexpected error lurking in the change--if we're planning on putting this in 2.0.1.

@anntzer anntzer merged commit fb3a2eb into matplotlib:v2.0.x Jan 23, 2017
@anntzer
Copy link
Contributor
anntzer commented Jan 23, 2017

Merged, but I'm not entering the debate of whether to backport or not :)

@QuLogic QuLogic deleted the freetype-version branch January 23, 2017 21:49
@anntzer
Copy link
Contributor
anntzer commented Jan 23, 2017

Apparently this went into 2.0.x, not master (I just clicked the green button). Someone please check whether this was correct...

@QuLogic QuLogic changed the title [MRG+1] Fix inverted expected/found FreeType version warning. Fix inverted expected/found FreeType version warning. Jan 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0