Next release 0.7.0

[tpaviot]

There has been quite a lot of work since the last release, I think it's time to release a new version. Todo before the release:

• [ ] Review the documentation. Make sure it is up to date with recent changes
• [ ] Review the README
• [ ] Update version number in setup.py, init and everywhere
• [ ] Review the notebooks that are not part of the documentation
• [ ] Anything else?

[dreinon]

Merging unmerged branches.

[tpaviot]

Unmerged branches are unsuccessful attempts, they can't be merged as is, but I keep them open because they contain some code that could be useful in the future

[dreinon]

What about my contributions to max-utilization branch? I did a PR to that branch instead of to master.

[tpaviot]

I can't see any pending pull request, did I miss something?

[dreinon]

I contributed changes to the max-utilization branch, but now those changes have to be added to master branch. Since both branches belong to your repo, I can't open a PR from tpaviot/max-utilization to tpaviot/master.

[tpaviot]

You can rebase your changes on top of master and submit a new PR

[dreinon]

Hi! What's still left to be done?

[tpaviot]

Update documentation. WIP.

[dreinon]

May I help w something?

[tpaviot]

See https://processscheduler.readthedocs.io/en/latest/, sections First order logics/Indicator and Objective/Solving still need to be reviewed

[tpaviot]

dev branch is here: https://github.com/tpaviot/ProcessScheduler/tree/update-doc

[dreinon]

Ok, I'll do that!

[dreinon]

Don't you think not_ should accept only one parameter since it's a unary operator? Now it accepts a list and adds the constraint Not(And(list)). I think that if the user want to achieve that, then they should use And(map(not_, list)) for example.

[tpaviot]

@dreinon you're right.

[tpaviot]

0.7.0 released and uploaded to pypi