8000 CI: pin 1.5.x cycler to 0.9.0 by tacaswell · Pull Request #6012 · matplotlib/matplotlib · GitHub
[go: up one dir, main page]

Skip to content

CI: pin 1.5.x cycler to 0.9.0 #6012

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
Feb 17, 2016
Merged

Conversation

tacaswell
Copy link
Member

No description provided.

@tacaswell tacaswell added this to the 1.5.2 (Critical bug fix release) milestone Feb 16, 2016
WeatherGod added a commit that referenced this pull request Feb 17, 2016
@WeatherGod WeatherGod merged commit e6f187a into matplotlib:v1.5.x Feb 17, 2016
@tacaswell tacaswell deleted the tst_pin_cycler branch February 17, 2016 00:37
@jenshnielsen
Copy link
Member

I assume this is only for making sure we test 0.9.0? We need to be careful when merging this forward to making sure this doesn't land on 2.x

@tacaswell
Copy link
Member Author

There are a bunch of new features in 0.10 that I think we do not want to
leak down to 1.5 to be conservative about version requirements.

On Wed, Feb 17, 2016, 03:52 Jens Hedegaard Nielsen notifications@github.com
wrote:

I assume this is only for making sure we test 0.9.0? We need to be careful
when merging this forward to making sure this doesn't land on 2.x


Reply to this email directly or view it on GitHub
#6012 (comment)
.

@jenshnielsen
Copy link
Member

That absolutely makes sense to me

@tacaswell
Copy link
Member Author

When I did the merge cascade up I made sure to not move this change over

04dce81

I think that means future merges will also not try to move this change.

@jenshnielsen
Copy link
Member

Yes great thats my understanding too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4BD0 None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0