... | ... | @@ -54,7 +54,7 @@ __Please update this document during your reign as release manager! Move all out |
|
|
## [3 weeks] prior to the release:
|
|
|
* __Check remaining tasks:__
|
|
|
Check all open MRs and Issues for severity and impact. Make changes to the planned milestone and comment as needed.
|
|
|
- __[Buildbot]__: Make sure Buildbot is configured to test the master with the correct dependencies. Continue to check the Buildbot daily for failing automatic tests. If there are any failing tests or build issues, create an issue and document this in the milestone issue.
|
|
|
- __CI__: Make sure the [automatic CI](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/pipelines) is configured to test the master with the correct dependencies. Continue to check the CI daily for failing automatic tests. If there are any failing tests or build issues, create an issue and document this in the milestone issue.
|
|
|
- __Edit the milestone issue:__ Update the milestone issue (e.g. [Release Issue 3.2](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/issues/829)). Clearly document which issues are still open, which MRs still need to be merged. This will act as a list of "announced changes". If there are open issues that need to be fixed for the release, but have not been assigned, assign them to one of the LH2 developers.
|
|
|
- __Announce soft feature freeze:__ This is the last opportunity to __announce__ changes to release manager, i.e. by adding a comment to the release issue in gitlab task and setting the milestone in the gitlab issue to the release. See email examples [here](#example-emails)
|
|
|
- __Subtask Check-in:__ Check in with the managers of the sub-tasks. Make sure anyone who needs further assistance or guidance gets it.
|
... | ... | @@ -119,7 +119,7 @@ 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.
|
|
|
|
|
|
* __Buildbot:__ Reconfigure buildbot to test both master and the release branch with the planned configurations. Continue to check the [buildbot daily](https://git.iws.uni-stuttgart.de/buildbot/) for failing automatic tests.
|
|
|
* __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.
|
|
|
|
|
|
* __Local Testing:__
|
|
|
-`dune` __versions__: Set up a DuMu<sup>x</sup> environment with each of the dune environments DuMu<sup>x</sup> will
|
... | ... | @@ -142,7 +142,7 @@ modules is documented in the dune.module file in the main folder. |
|
|
|
|
|
__Final testing!__
|
|
|
|
|
|
* __Re-run tests:__ Regularly re-run `make headercheck`, `make package source`, all tests, and check the [buildbot daily](https://git.iws.uni-stuttgart.de/buildbot/).
|
|
|
* __Re-run tests:__ Regularly re-run `make headercheck`, `make package source`, all tests, and check the [CI daily](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/pipelines).
|
|
|
|
|
|
* __Update copyright:__ Check if every file has the correct and not the outdated copyright notice. You
|
|
|
can list files that contain the old notice with executing
|
... | ... | @@ -205,10 +205,6 @@ of the last commit for the current release. |
|
|
Bernd has the account details and can help you with this. It would be helpful to prepare a list of those
|
|
|
who should be included in the citation as authors beforehand.
|
|
|
|
|
|
* __Website:__
|
|
|
- Include the Zenodo citation online.
|
|
|
- Link the release tarballs correctly.
|
|
|
|
|
|
* __Write release email:__ Write an email to dumux@listserv.uni-stuttgart.de, include any noteworthy
|
|
|
changes made in this release. See email examples [here](#example-emails).
|
|
|
|
... | ... | @@ -222,8 +218,7 @@ colleagues too. |
|
|
in the changelog.
|
|
|
|
|
|
* Email the dumux mailing list with updates about things that are to be supported, or things that will
|
|
|
no longer be supported in the next release (different dune versions, compilers, changes to the buildbot,
|
|
|
etc.)
|
|
|
no longer be supported in the next release (different dune versions, compilers, etc.)
|
|
|
|
|
|
## Appendix
|
|
|
|
... | ... | @@ -325,5 +320,4 @@ __Past announcements of the DuMu<sup>x</sup> release__ |
|
|
[DuMu<sup>x</sup>-Lecture]: https://git.iws.uni-stuttgart.de/dumux-repositories/dumux-lecture
|
|
|
[DuMu<sup>x</sup>-Course]: https://git.iws.uni-stuttgart.de/dumux-repositories/dumux-course
|
|
|
[issues]: https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues
|
|
|
[MRs]: https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/merge_requests
|
|
|
[Buildbot]: https://git.iws.uni-stuttgart.de/buildbot/ |
|
|
\ No newline at end of file |
|
|
[MRs]: https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/merge_requests |
|
|
\ No newline at end of file |