| | 1 | = Release team working process = |
| | 2 | |
| | 3 | This is the way the release team is supposed to work. |
| | 4 | |
| | 5 | == Overview == |
| | 6 | The release team process consists of the following activities: |
| | 7 | * Opening |
| | 8 | * Testing |
| | 9 | * Reviews |
| | 10 | * Release assembly |
| | 11 | |
| | 12 | == Opening == |
| | 13 | This is the first things that the team should do after the official sprint opening: |
| | 14 | * Create a branch from the trunk. The name should be further determined(perhaps something like release01 or release01-pre-alpha-2) |
| | 15 | * Create a wiki page for the release. This will be ITERATION_<it_number>/Release |
| | 16 | * Select tasks for testing. Sort them by their testability and importance |
| | 17 | * Merge back valuable changes done on the previous release branch into the trunk |
| | 18 | |
| | 19 | == Testing == |
