Release 2.4.0

[nelekoehler]

Release date: 2024-07-01
Release team: @christian-rli @NormanZielke @nelekoehler

[l-emele]

In the pad of yesterday's dev meeting, I read the following sentence:

Release wird voraussichtlich sehr klein. Version 2.3.1 statt 2.4.0??

Please keep in mind, that we use Semantic Versioning. For the OEO we translated this to:

1. Major version if something fundamental changes (e.g. file structure, switch from named identifiers to numerical identifiers, big restructuring)
2. Minor version if content was added (new classes etc.)
3. Patch version if only a bug was fixed but nothing else.

We still have a month until the release, so I hope we finalise at least PRs #1788 and #1840 which both bring new content.

[nelekoehler]

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.4.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, @MGlauer and @jh-RLI.

Detailled release workflow

[stap-m]

Thanks for the release! As stated in the updated release workflow, @jh-RLI has to be informed as well.

[jh-RLI]

I will update the oeo version on the oep. Previously, the build-files.zip contained additional folder´s one named "oeo" and one with the version identifier as name (see previous version). I think we should include this folder again in the next release. Then the structure is harmonised again :)