GRASS 7 Tech-Preview: Difference between revisions
Jump to navigation
Jump to search
⚠️Mlennert (talk | contribs) |
⚠️Mlennert (talk | contribs) (→Tasks) |
||
| Line 6: | Line 6: | ||
==Tasks== | ==Tasks== | ||
* Check current state of bug reports, especially critical ones, possibly reclassifying some if needed | |||
* Make decision on calendar, especially making sure that sufficient developers are available for bug fixing during freeze and users for testing | |||
* Declare feature freeze, limiting commits to bug fixes (possibly limiting svn write access temporarily ?) | |||
* Bug fixing sprint | |||
* After one week, release a RC | |||
* Testing and bug fixing sprint | |||
* After two weeks, release tech-preview | |||
* Open svn to general development again | |||
==Calendar== | ==Calendar== | ||
Revision as of 12:01, 13 May 2013
Objectifs
- Take a step back to where we are at with Grass 7
- Enlarge user base of Grass 7 to increase number of testers
- Create a fixed target for binaries that could be included in distributions
Tasks
- Check current state of bug reports, especially critical ones, possibly reclassifying some if needed
- Make decision on calendar, especially making sure that sufficient developers are available for bug fixing during freeze and users for testing
- Declare feature freeze, limiting commits to bug fixes (possibly limiting svn write access temporarily ?)
- Bug fixing sprint
- After one week, release a RC
- Testing and bug fixing sprint
- After two weeks, release tech-preview
- Open svn to general development again