-
Notifications
You must be signed in to change notification settings - Fork 251
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
tagging 0.7 #1140
Comments
backburner for me right now. Hope to get to it some time after May 10. |
I've been using master for the past couple weeks and it's performed well for me. I think that we need to tag and push it out because Gadfly is interfering with the rest of the dataframes ecosystem. We'll have to accept the regression on #1130 until @andreasnoack has a chance to look into it. |
agreed. specifically, see #1144. @andreasnoack please let us know your timeframe so we can decide whether to tag now or wait. we appreciate all you work on the dataframes issue! |
i'm inclined to tag this weekend unless someone convinces me it's a bad idea. [EDIT: because there were two more gripes recently on slack about the dataframes incompatibility). |
I would urge a tag, even with some regressions, as soon as possible. The dependence of Gadfly on old DataFrames has unfortunately caused a huge split, with many strange dependencies. Did you know for example, that if you install Gadfly, you cannot now install a new version of ZMQ? (The reasons are arcane, and honestly not the Gadfly developers problem, just an unfortunate side effect -- but still something that is very painful for many users). |
tagging now |
Merged. |
Thanks! |
close by JuliaLang/METADATA.jl#14746 |
would be good to tag a new release which fixes the dataframes problem. are there any PRs we should merge before hand?
@Mattriks since #1118 introduces a breaking change, would be good to do that now as otherwise we'd have to wait awhile.
@non-Jedi what is your time frame for #1105 ?
i've been diligently working on #1116, but that is something that could wait.
The text was updated successfully, but these errors were encountered: