|
|
|
# Release Manager Tasks
|
|
|
|
|
|
|
|
__Authors__: C. Grüninger (2.1), T. Fetzer (2.3), A. Kissinger (2.4), K. Weishaupt (2.9), J. Hommel (2.10), S. Ackermann (2.11), K. Heck(3.1), E. Coltman(3.2), K. Weishaupt (3.3)
|
|
|
|
|
|
|
|
Most Recent Release: [DuMu<sup>x</sup> 3.3](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/tags/3.3.0) , 2020-11-13
|
|
|
|
|
|
|
|
## Introduction
|
|
|
|
|
|
|
|
Congratulations! You've made it through the long and tough selection process
|
|
|
|
and have been chosen to be the next DuMu<sup>x</sup> release manager. Please use this document
|
|
|
|
as a step-by-step guide through the tasks and procedures that accompany this job.
|
|
|
|
In the appendix you will find useful links, hints, and other things you may want to know about, as well
|
|
|
|
some examples of old announcement emails.
|
|
|
|
|
|
|
|
__Please update this document during your reign as release manager! Move all outdated material to the appendix.__
|
|
|
|
|
|
|
|
## [5 Weeks] prior to the release:
|
|
|
|
* __Call a meeting__: Contact all of the primary DuMu<sup>x</sup> 3.3 developers (LH2 employees) and organize a meeting. If possible, line this up with a dumuxDay. Tasks \ref{major_subtasks}, \ref{createmilestone}, \ref{dunecompat}, \ref{gothroughtasks}, and \ref{assign} should all be done and addressed during this meeting.
|
|
|
|
* __Assign developers to the major subtasks__:
|
|
|
|
- Doxygen Tasks: compile, remove warnings, check module/class descriptions.
|
|
|
|
- Handbook Tasks: Update the Handbook & [Changelog](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/blob/master/CHANGELOG.md). Make sure everything is up to date.
|
|
|
|
|
|
|
|
|