chore: merge v0.2.0 into master #111
Conversation
* refactor: change set_parameter to set_optimizer_attribute * doc: update README to reflect new JuMP compatibility * chore: update JuMP dependency to 0.21.3 * chore: update Manifest.toml to reflect JuMP v0.21.3
* refactor: use new DataFrames groupby syntax * refactor: use innerjoin instead of join for DataFrame * chore: update DataFrames compatibility from 0.20 to 0.21 * chore: update Manifest.toml for DataFrames 0.21.4
Add github action to check formatting
…threads_from_python feat: select number of gurobi threads from python
feat, refactor: add new entry point to run call.py without PowerSimData
docs: update documentation for args used to run scripts
…data.py afterward chore: remove extra print statements
…actor Anna/extract data refactor
refactor: remove Gurobi requirement
Non blocking reads from process output
|
I think the release note is a bit too long. Maybe for now just list the key features/fixes that were added in this release. What we will aim for in the future is having a link to the detailed release note on a separate page. |
|
@kasparm ideally we will be doing this more than once per year, so future ones will be shorter. What do you think about separating the 'merged PRs' section into 'features' (anything the user will see) and 'fixes etc.' (bug fixes, CI stuff, documentation)? |
|
@danielolsen that is fine with me for now. As said for the future we would like these reports on github short and and have a more detailed report on a separate page. |
|
@kasparm I edited the proposed note above. |
|
Looks good. Don't forget to change the version number in Project.toml |
Done |
Purpose
Update
master, after which we will add av0.2.0tag.Proposed release notes
Closed Issues:
Merged pull requests (features):
Merged pull requests (fixes etc.):
Time to review
15 minutes? I guess it depends how long it takes for us to decide what our release notes should look like.