List view
- No due date•19/19 issues closed
- No due date•29/29 issues closed
- No due date•4/4 issues closed
- No due date•5/5 issues closed
- No due date•34/34 issues closed
- No due date•2/2 issues closed
- Due by March 31, 2022•51/51 issues closed
- No due date•8/8 issues closed
- No due date•30/30 issues closed
- No due date•4/4 issues closed
- No due date•26/26 issues closed
- No due date•1/1 issues closed
- No due date•3/3 issues closed
- No due date
- No due date•1/1 issues closed
- No due date•3/3 issues closed
- No due date
- No due date
- No due date•3/3 issues closed
- No due date•1/1 issues closed
- No due date•7/7 issues closed
- No due date•8/8 issues closed
- Due by March 31, 2017•6/6 issues closed
Minor release. See CHANGES.md for more details
Due by January 23, 2017•18/18 issues closedSee [release 4.0.0](https://github.com/chocoteam/choco-solver/releases/tag/untagged-7b156e8b13eed9bd1ba7) for more details.
No due date•13/13 issues closedSee [release 4.0.1](https://github.com/chocoteam/choco-solver/releases/tag/untagged-1919e143c720b2c5dd4b) for more details.
No due date•16/16 issues closedAPI refactoring: - move `Solver` to `Model` and `SearchLoop` to Solver`. It aims at separate purposes: first modeling then solving. - move `VariableFactory` and `*ConstraintFactory` directly into `Model`, for instance: `model.intVar("X", 0, 10)` or `model.allDifferent(Y).post();`. It aims at limiting entry points for users to a single one, `Model`, and reducing API size (without the necessity to always declare the model). - move `Chatterbox` to `Solver` to limit entry points and reduce APIs. - reduce resolution API to one: `solve()` instead of `find*`. It aims at letting the user configure the resolution once, and then iterate over solutions. Moreover, even if helper should remain to solve COP, the way cuts are added should be open and easy (e.g., multi objectives resolution or ad hoc cut). - remove `ISolutionRecorder`: nothing is done by default regarding solutions, but recording (user specific) solution is made easy with `Solver.solve()`.
Due by May 31, 2016•16/16 issues closed- Due by December 21, 2015•14/14 issues closed
We delayed the release in order to fix: - the parallel framework (we are not completely satisfied of the current version), - to integrate the results of the last MZN 2015 challenge, - to revamp the search loop.
Due by November 19, 2015•24/24 issues closedBug fixes
Due by May 13, 2015•20/20 issues closed+ Support for Java8. + change package name from choco to org.choco-solver to enable publication on maven repo + remove deprecated methods (there are only few)
Due by December 19, 2014•13/13 issues closedMinor release : - release dedicated to choco-parsers mainly. - clean up and stabilize dependencies - bug fixes
Due by December 5, 2014•6/6 issues closed- No due date•4/4 issues closed
Fix bugs in 3.1.1
Due by March 14, 2014Fixed version of 3.1.0
Due by November 13, 2013•16/16 issues closedThe next one! (the due is not strict): - Simplify API and propagation engine. - Add documentation
Due by March 28, 2014•23/23 issues closedFirst stable release of Choco3
Due by September 2, 2013•2/2 issues closed