GRASS 6.3 Feature Plan: Difference between revisions
Jump to navigation
Jump to search
(Category:Development) |
(raster maps: implement SQL based time series support) |
||
| Line 15: | Line 15: | ||
* Make sqlite the default DB? | * Make sqlite the default DB? | ||
* Create GRASS Addons SVN repository and really use GEM | * Create GRASS Addons SVN repository and really use GEM | ||
* drop d.m display manager (as unmaintained; there is gis.m and/or a python based GUI) | * drop d.m display manager (as now almost unmaintained; there is gis.m and/or a python based GUI) | ||
* raster maps: implement SQL based time series support | |||
=== Wishes === | === Wishes === | ||
Revision as of 21:25, 5 August 2006
GRASS 6.3.x feature plan
About feature plan
To make GRASS releases more often and more predictable, here is GRASS next releases feature plan. This feature plan has to be filled by developers working on GRASS 6.3.
Basic principles:
- Add a short feature description, bug No., etc. what You want to see and what YOU will implement or fix in upcoming GRASS 6.3 to #TODO list. Sign it using four tildes ~~~~!
- If You work on it, and You think it will make to next release, MOVE to #In progress section.
- When You finish and commit Your work, MOVE it to #Finished section.
Warning After freeze start, You will not be able to commit any new features till freeze end. Only bugfixes and commits related to items listed in In progress section.
TODO
- Make sqlite the default DB?
- Create GRASS Addons SVN repository and really use GEM
- drop d.m display manager (as now almost unmaintained; there is gis.m and/or a python based GUI)
- raster maps: implement SQL based time series support
Wishes
- Create 3D animation w nviz showing GRASS 3D coolness. MarisN 12:00, 4 August 2006 (CEST)