... | ... | @@ -27,7 +27,7 @@ __Please update this document during your reign as release manager! Move all out |
|
|
- [Examples suite](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/tree/master/examples) Tasks: Make sure everything compiles, remove all warnings, and check to see that the tests pass. Make sure the READMEs are up to date.
|
|
|
<br/>
|
|
|
|
|
|
* __Create a milestone:__
|
|
|
* __Create a group (dumux-repositories) milestone in GitLab:__
|
|
|
- As this release relates to multiple git projects ([DuMu<sup>x</sup>], [DuMu<sup>x</sup>-Lecture], [DuMu<sup>x</sup>-Course]), mark the release milestone in the \dumux-repositories group. As an example, here are the milestones for [DuMu<sup>x</sup> 3.3](https://git.iws.uni-stuttgart.de/groups/dumux-repositories/-/milestones/4), [DuMu<sup>x</sup> 3.2](https://git.iws.uni-stuttgart.de/groups/dumux-repositories/-/milestones/2). and [DuMu<sup>x</sup> 3.1](https://git.iws.uni-stuttgart.de/groups/dumux-repositories/-/milestones/3). Within this milestone, list the dates for the feature freezes, the testing, and the release, as well as the people responsible for the major subtasks (See \ref{major_subtasks}: handbook, doxygen, website...).
|
|
|
<br/>
|
|
|
|
... | ... | @@ -109,8 +109,6 @@ in the DuMu<sup>x</sup> -stable top folder. Use what the script recommends to ad |
|
|
* __Run create cmakelists__: Run the `bin/util/create cmakelists.py` script in `dumux/dumux`, in order
|
|
|
to update the cmakelists in the source directory.
|
|
|
|
|
|
* __Tarballs__:Try building the tar ball make package source in the build directory and fix possible bugs
|
|
|
|
|
|
* __Release Branches: For each DuMu<sup>x</sup> module, create a new branch titled releases/X.Y.__ (e.g., [DuMu<sup>x</sup> 3.3](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/tree/releases/3.3), [DuMu<sup>x</sup>-Lecture 3.3](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux-lecture/-/tree/releases/3.3), [DuMu<sup>x</sup>-Course 3.3](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux-course/-/tree/releases/3.3)
|
|
|
|
|
|
-Create new branch: `git checkout -b releases/X.Y`
|
... | ... | @@ -191,7 +189,7 @@ See email examples [here](#example-emails). |
|
|
|
|
|
__Important__ These steps are normally done together with Bernd. Make sure to schedule the time properly.
|
|
|
|
|
|
* __Protect Branches:__ Go to gitlab and make the [release branch](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/protected_branches) protected. Select the release branch to protect. In the ”allowed to merge” column, select maintainers. In the
|
|
|
* __Protect release branches (in GitLab):__ Go to gitlab and make the [release branch](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/protected_branches) protected. Select the release branch to protect. In the ”allowed to merge” column, select maintainers. In the
|
|
|
allowed to push column, select no one, then press select. This means that the branch can only be
|
|
|
modified via a merge request merged by a maintainer.
|
|
|
|
... | ... | @@ -329,7 +327,3 @@ __Past announcements of the DuMu<sup>x</sup> release__ |
|
|
[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 |
|
|
|
|
|
|
|
|
|
|
|
|