-
Notifications
You must be signed in to change notification settings - Fork 26
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
Maintenance of repo #51
Comments
We could consider moving this to jump-dev. I don't think @martinbiel isn't active on GitHub anymore, but I'll email him. |
Hey! Bumping versions so that SPjl does not downgrade should not be too much of a hassle. In the long term, a more involved rewrite of the backend is required to achieve an implementation less dependent on the MOI version. I was awaiting stable versions of JuMP/MOI before starting on that, but since then new work and fathering twins got in the way 😅. I have added @odow as a collaborator to help out with the maintenance. In the long term, moving the repo to jump-dev is probably sensible 🙂. |
@avinashresearch1 happy to review/merge PRs. |
Amazing, thanks @odow and @martinbiel. I have a local clone I worked on during the holiday break and wrote another example, let me clean up and send a PR. I also have some CI minutes so can run tests on my fork before it is merged. Congrats @martinbiel on the twins :) |
I'm looking to build additional tooling for two-stage stochastic programs and ran across this excellent modeling package. The issue is it appears to have fallen behind on maintaining compat with the updates in JuMP, MathOptInterface and certain solvers (as other folks have pointed out).
Would you be open to transferring ownership (probably to JuMP-dev ?) or giving admin rights to new folks who can help take over maintenance? I can volunteer to maintain the package (compat etc.). Alternatively, I am considering factoring out a new repo (say called
StochasticProgrammingModels.jl
with files from /src/macros and updating that to fit JuMP syntax (in the spirit of having packages only doing one thing). Please let me know your thoughts.The text was updated successfully, but these errors were encountered: