Blog post for JuMP 1.0 release #71
Merged
+432
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
blegat
reviewed
Feb 23, 2022
blegat
reviewed
Feb 23, 2022
|
|
I've made some updates. Please chime in with feedback. |
|
Sorry I haven't gotten to look at this yet. I'll do a pass on Friday. |
|
Yeah no rush. But we're looking pretty healthy on the jump-dev/JuMP.jl#2564 front. So once this is ready we're pretty much good to release JuMP 1.0. |
mlubin
reviewed
Mar 11, 2022
mlubin
approved these changes
Mar 13, 2022
6 tasks
|
@IainNZ @joaquimg @joehuchette @blegat please approve since you're listed as co-authors :) |
|
Exciting! |
joaquimg
approved these changes
Mar 20, 2022
blegat
reviewed
Mar 24, 2022
Co-authored-by: Benoît Legat <benoit.legat@gmail.com>
blegat
approved these changes
Mar 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mainly an initial draft with lots of room for improvement. We should discuss this on the monthly developer call.