| ... | ... | @@ -16,7 +16,9 @@ __Please update this document during your reign as release manager! Move all out |
|
|
|
|
|
|
|
## 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:
|
| ... | ... | |
