upgrade to scip 4.0 about csip HOT 12 CLOSED

What does it mean to support the new SCIP, can't we support both?

Does any of the code of CSIP change because of that? If so, then we require the user to install the new SCIP, which I feel is a breaking change, so we should go to 0.4.0.

from csip.

Well, there is a single line of code changed in CSIP.

I guess we could support both, but why?

from csip.

Then the update is not a breaking change, and people who update SCIP.jl with Julia's package manager don't end up with a broken system.

On the other hand, users would not even know about the new SCIP...

@mlubin : Do you have an opinion on this?

from csip.

it is not a breaking change, but it will just not compile with SCIP 3.2.1, or am I missing your point?

from csip.

Yes, so an update of SCIP.jl will tell them that CSIP is out-of-date, but if the user then deletes CSIP (as instructed) and runs Pkg.build("SCIP") it will fail.

from csip.

why will it fail? scip 4 is out now ;)

from csip.

Users still have to download and install it, nothing is automated.

from csip.

yeah, but that has always been then case, right?

from csip.

Given that everything is already manual, it's okay with me if an update to SCIP.jl results in a broken system. However, it would be nice to provide a useful error message, e.g., as we do with ECOS. Whoever wants to keep using the old version of SCIP can pin SCIP.jl.

from csip.

Well, we have that error message in SCIP.jl, but refering to CSIP, not SCIP.

@fserra: Didn't you already have a pull request with a one-line change? We should then also update the README and be explicit about SCIP's version.

from csip.

yeah sure. So what is it then? 0.4.0 or 0.3.7??

from csip.

Go for 0.4.0.

from csip.