@@ -14,6 +14,11 @@ some examples of old announcement emails.
...
@@ -14,6 +14,11 @@ some examples of old announcement emails.
__Please update this document during your reign as release manager! Move all outdated material to the appendix.__
__Please update this document during your reign as release manager! Move all outdated material to the appendix.__
## Beginning of the release cycle:
* __Think about manpower__: Contact developers, especially LH2 members, and ask them if they are here/ have time.
* __Create focus points__: On the first Dumux day of the new release cycle, destill a few (maybe 3) key points one wants to focus on during the next release. This can be done by looking through issues or talking to people.
* __Assign groups__: For each key point designate a group that will only work on this specific point during the release. Make sure that groups are mixed in their experience levels.
## [5 Weeks] prior to the release:
## [5 Weeks] prior to the release:
* __Call a meeting__: Contact all of the primary [DuMu<sup>x</sup>] developers (LH2 employees) and organize a meeting. If possible, line this up with a DuMu<sup>x</sup> Day. The following tasks should all be done and addressed during this meeting.
* __Call a meeting__: Contact all of the primary [DuMu<sup>x</sup>] developers (LH2 employees) and organize a meeting. If possible, line this up with a DuMu<sup>x</sup> Day. The following tasks should all be done and addressed during this meeting.
