Closed blegat closed 7 years ago
I think JuliaOpt/JuMP.jl#1023 qualifies as a bug fix, so we could/should have a new patch release.
@joehuchette it's fixing a bug that was never in any release IIRC. That doesn't necessarily trigger a new release.
Possibly, I was trying to trace the lineage but got lost.
Could we register StructJuMP once this PR is merged ?
Releasing should probably wait for a compatible released version of JuMP. @blegat what JuMP commits does this rely on? If it's not invasive we could potentially cherry-pick onto a new patch release. Or just release a new JuMP version, any objections @mlubin?
I can't be involved in any JuMP releases before June 5th (thesis). But I'd be ok with tagging 0.17 once the currently active PRs go through.
I have rebased the PR so that it no longer checkout JuMP and I have added JuMP v0.17
as a dependency :)
Good to merge once Travis clears!
Travis succeeds on v0.5 and the failure on nightly/v0.7 is due to compilation errors on dependencies. The coverage has decreased because a lot of lines removed where covered. However the number of lines missed has decreased too ! :)
What about registering StructJuMP now that this PR is merged ? :)
Sounds good! I won't be able to tag and register before this weekend, but feel free to do it yourself.
Thanks! Unfortunately, I don't have the sufficient rights to do it :(
I added you as collaborator, which should fix that.
Thanks :)
We need https://github.com/JuliaOpt/JuMP.jl/pull/1023 to be merged for this PR to work