Release 3.7
This a release issue template with a checklist based on Release Manager Tasks. Check there for details on each task.
[5 Weeks] prior to the release:
-
Call a meeting -
Assign developers to the major subtasks -
Create a group (dumux-repositories) milestone in GitLab -
Fix planned [Dune] and compiler compatibility - Dune 2.9 / 2.10-git with C++17 compiler (gcc and clang)
- Compilable with C++20 compiler (gcc and clang)
-
Go through all existing Gitlab tasks ([issues] or [MRs]) -
Assign the open [issues] and [MRs] to the developers -
Post a release schedule announcement on the mailing list
[3 weeks] prior to the release:
-
Check all open MRs and Issues for severity and impact -
Update the milestone issue -
Announce soft feature freeze on the mailing list -
Check in with the managers of the sub-tasks
[2 weeks] prior to the release:
Hard Feature Freeze!
-
Check remaining MRs and Issues -
Update the milestone issue -
Generate example documentation with the script generate_example_docs.py -
Update CHANGELOG -
Announce hard feature freeze on the mailing list -
Update all install scripts and the install text in the handbook -
Header check (run make headercheck
) -
Re-generate parameter list ( bin/doc/generate_parameterlist.py
) and check log file (maybe manual updates tobin/doc/docextra/parameters.json
are needed) -
Make sure the CMakeLists.txt in dumux
subfolder are up-to-date (generated withbin/create_cmakelists.py
, dumuxmake install
should result in a usable installed dumux version) -
Create release branches -
Configure CI to test release branch -
Local Testing (different compilers and dependency setups)
During the week of the release:
Final testing!
-
Re-run tests -
Update copyright -
Update License (!3442 (merged)) -
Test Lecture and Course -
Update Website -
Create a release candidate -
Call for testing
Releasing DuMux
Important: These steps are normally done together with Bernd. Make sure to schedule the time properly.
-
Make sure the release branch has the right version in dune.module
-
Make sure the CI on the release branch is not testing against Dune master anymore -
Protect release branch (in GitLab) -
Create new tags -
Prepare a Darus citation -
Include the Zenodo citation to the website (only major releases)
After the release
-
Bump version in dune.module to next version -
Write a release email to dumux@listserv.uni-stuttgart.de about updates on supported features and upcoming changes
Edited by Hamza Oukili