9 | | * Check current state of bug reports, especially critical ones, possibly reclassifying some if needed |
10 | | * Make decision on calendar, especially making sure that sufficient developers are available for bug fixing during freeze and users for testing |
11 | | * Declare feature freeze, limiting commits to bug fixes (possibly limiting svn write access temporarily ?) |
12 | | * Bug fixing sprint |
13 | | * After one week, release a RC |
14 | | * Testing and bug fixing sprint |
15 | | * After two weeks, release tech-preview |
16 | | * Open svn to general development again |
| 9 | * Check current state of bug reports, especially critical ones, possibly reclassifying some if needed |
| 10 | * Make decision on calendar, especially making sure that sufficient developers are available for bug fixing during freeze and users for testing |
| 11 | * Declare feature freeze, limiting commits to bug fixes (possibly limiting svn write access temporarily ?) |
| 12 | * Bug fixing sprint |
| 13 | * After one week, release a RC |
| 14 | * Testing and bug fixing sprint |
| 15 | * After two weeks, release tech-preview |
| 16 | * Open svn to general development again |