2.0.0

[l-emele]

I start here the discussion for the next release.

I just adapted the release milestones:

• In the last OEO dev meeting, we moved the release date to 9 October. I just updated the release milestone and renamed it to oeo-release-2.0.0-restructuring.
• Additionally, I renamed the existing milestone oeo-release-1.17.0 to oeo-release-2.0.0-thematical as it collects all issues that are not related to the restructuring, but will also be part of the 2.0.0 release.¹ This milestone currently has still 87 open issues, so we have to sort out a lot.
• I renamed the milestones 1.18.0 and 1.19.0 to 2.1.0 and 2.2.0 accordingly and set for the latter a release date in line with the Release cycle #1588.

Footnotes

1. So in this exceptional case we have two milestones, but is justified as the 2.0.0 is mainly because of the restructuring, but of course also contains thematic additions. ↩

[stap-m]

Due to a high work load for this major release, we reset the date to Oct 24. Release team: @l-emele @nelekoehler @stap-m

[l-emele]

To do list for release:

1. All issues closed and all pull requests merged that are part of the release milestone.
2. Branch releases-v1.2.3 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

[stap-m]

Done with the major release 2.0.0! 🎆 🥳

[stap-m]

Hotfix release 2.0.1:
To do list for release:

1. All issues closed and all pull requests merged that are part of the release milestone.
2. Branch releases-v1.2.3 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.