Release 3.6
This a release issue template with a checklist based on Release Manager Tasks. Check there for details on each task.
26 Aug 22 2 Sep 22)
[5 Weeks] prior to the release: (-
Call a meeting -
Assign developers to the major subtasks - Manager: @mathis
- Lecture: @stefaniekiemle
- Doxygen: @melaniel #1178 (closed)
- Handbook: @IvBu
- Course: @yue
- Examples: @Maziar
- Website: @RoWin
-
Create a group (dumux-repositories) milestone in GitLab -
Fix planned [Dune] and compiler compatibility (Dune 2.8/2.9-git, C++ 17 gcc9.3/clang10, CMake 3.13, Python 3.6) -
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 -
Schedule tasks / agend for coding day on 31 Aug 22
2 Sep 22 16 Sep 22)
[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
9 Sep 22 23 Sep 22)
[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/utils/create_cmakelists.py
, dumuxmake install
should result in a useable installed dumux version) -
Create release branches -
Configure CI to test release branch -
Local Testing (different compilers and dependency setups) -
Make sure there is no compiler warning in both local and CI setup (also lecture and course)
During the week of the release:
Final testing!
-
Re-run tests -
Update copyright -
Update License -
Test Lecture and Course -
Update Website -
Create a release candidate -
Call for testing
23 Sep 22 27 Oct 22)
Releasing DuMux (Important: These steps are normally done together with Bernd. Make sure to schedule the time properly.
-
Protect release branch (in GitLab) -
Create new tags -
Prepare a ZenodoDaRUS citation -
Include the DaRUS 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
Open issues and merge requests
-
#1165 (closed) / !3171 (merged) (separate base and extended richards models) -
#1182 (closed) (assemblers use fvGeometry information instead of element information) -
#1149 (closed) / !3270 (merged) (documentation of flux headers) -
#1185 (closed) / !3284 (merged) (tabulated component multithreading) -
!3288 (merged) (pq1bubble Navier-Stokes model) -
!3234 (merged) (basic gridgeometry) -
!2113 (closed) (only selected changes will be merged through separate merge requests) -
!3165 (merged) (stamped subgrid)
Edited by Bernd Flemisch