| ... | ... | @@ -84,9 +84,6 @@ where `TAG` is the tag of the last release (e.g. `3.4.0`) |
|
|
|
* __Announce Freeze:__ Announce hard feature freeze. Explain how no further changes to the code,
|
|
|
|
except for bugfixes and documentation will be accepted. See email examples [here](#example-emails).
|
|
|
|
|
|
|
|
* __Install Scripts:__ Update all install scripts and the install text in the handbook. Test them according
|
|
|
|
to the text in the handbook.
|
|
|
|
|
|
|
|
* __Header check:__ Check header files by running the command `make headercheck` with with both a minimal and a maximal setup in terms of Dune dependencies. To enable the `headercheck`, turn on
|
|
|
|
`headercheck` in the [cmake.opts file](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/blob/master/cmake.opts) (`DUMUX ENABLE HEADERCHECK = ON`). Look at the error message,
|
|
|
|
and include the correct headers in the failing header.
|
| ... | ... | @@ -123,6 +120,10 @@ git”) and commit the change. Push the branch: |
|
|
|
__From then on__, changes are still to be made to the master, but the merge commits should be
|
|
|
|
cherrypicked onto the releases/X.Y branch.
|
|
|
|
|
|
|
|
* __Install Scripts__: Update all install scripts on the release branch. Create a MR on master to update the installscripts accordingly, but only merge them after the release. We want that the installscript does not default to a unreleased release branch.
|
|
|
|
|
|
|
|
* __dune.module__: Change version from e.g. 3.9-dev to 3.9 on the release branch. Create a MR for master to bump the version. e.g. 3.9-dev to 3.10-dev. Again merge this after the release.
|
|
|
|
|
|
|
|
* __CI:__ Reconfigure [the CI](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/pipelines) to test both master and the release branch with the planned configurations. Continue to check the CI for failing automatic tests. In case you need to update or change the generated docker images, this can be done in [this file](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux-docker-ci/-/blob/master/.gitlab-ci.yml). The `dumux-docker-ci` repository contains the docker files for the images and its CI builds those images as well as uploads them to the image registry. Additionally, update the [scheduled pipelines](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/pipeline_schedules) to test your and the previous release branch as well as the master branch (keep that). If the DuMu<sup>x</sup> pipelines should be run with other docker images, adapt [this file](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/blob/master/.gitlab-ci.yml).
|
|
|
|
|
|
|
|
* __Local Testing:__
|
| ... | ... | |
