GRASS 6.2 Feature Plan: Difference between revisions
Jump to navigation
Jump to search
(GRASS 6.2 Feature Plan) |
(some done TODOs) |
||
Line 15: | Line 15: | ||
==== TODOs ==== | ==== TODOs ==== | ||
<strike> <!-- done --> | |||
* unlimited number of raster map (r.patch, r.series etc) | |||
* several MinGW fixes for native MS-Windows support | |||
* several fixes for MS-Windows/Cygwin support | |||
</strike> | |||
* Add the new v.lidar.* tools (needed for FOSS4G2006) | * Add the new v.lidar.* tools (needed for FOSS4G2006) |
Revision as of 12:47, 7 August 2006
GRASS 6.2.x feature plan
There will be a release branch for 6.2.x, see details at CVS: tags and branches. A release branch is considered as "frozen", only bugfixes can be done.
GRASS 6.2.0
MNs suggestions are:
- do the proposed bug day soon (in August '06)
- don't submit changes to CVSA HEAD with heavy impact during this short time
- End of August '06:
- create a new branch for 6.2, maintain it for a while
- rename 6.1-CVS HEAD to 6.3-CVS HEAD to enable developers again to submit complex changes. Maybe a few things can be anticipated from the GRASS 7 ideas_collection (respecting our rules to keep parameters/flags/behaviour as much as possible for the 6.x series)
In general 6.2 should not deviate too much from the current 6.1-CVS HEAD to avoid a major delay.
TODOs
- unlimited number of raster map (r.patch, r.series etc)
- several MinGW fixes for native MS-Windows support
- several fixes for MS-Windows/Cygwin support
- Add the new v.lidar.* tools (needed for FOSS4G2006)
- nviz vertical exaggeration (if not fixed in 6.1)
- write impressive press release (in CVS Web)
Releases
- It would be great to have it available for the FOSS4G2006 conference in September (so, 5th September).