Release 2.1.0

[l-emele]

The next release is planned on 2023-12-04 which is a Monday and is only 13 days from today.

The release milestone currently holds 94 open and 4 closed issues.

Do we have already have assigned a release team?

Here is the to do list for this release:

1. All issues closed and all pull requests merged that are part of the release milestone.
2. Branch releases-v2.1.0 from dev.
3. Update version information and release date in VERSION file and CITATION.cff.
4. Change unreleased heading in CHANGELOG.md.
5. Create two pull requests.
6. Automated tests are successful.
7. PR reviews.
8. Merge both PRs.
9. Close release milestone.
10. Draft release.
11. Set as the latest release.
12. Press Publish release button.
13. Create new unreleased section in CHANGELOG.md.
14. Add build files to the release page.
15. Inform @adelmemariani and @MGlauer.

Detailled release workflow

[l-emele]

I went through all issues of milestone 2.1.0, commented on some, and move others. This reduced the total of open issues to 76 and at least four of them are ready for implementation.

[stap-m]

Release team: @areleu @nelekoehler @chrwm
Release will be done on 2023-12-05

[l-emele]

Is there a reason why this release is not available on the OEP? There is still version 2.0.1.

[stap-m]

As annouced by @jh-RLI, oeo will be updated with the next oep release this time, which is planned for this week.