GRASS 6.3 Feature Plan: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
No edit summary
 
Line 2: Line 2:
=== About feature plan ===
=== About feature plan ===


To make GRASS releases more often and more predicitble, here is GRASS next releases feature plan. This feature plan has to be filled by developers working on GRASS 6.3.
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:
Basic principles:
# Add a short feature description, bug No., etc. what You want to see an what '''YOU will implement or fix''' in upcoming GRASS 6.3 to ''[[#TODO]]'' list. Sign it using four tildes <nowiki>~~~~</nowiki>!
# 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 <nowiki>~~~~</nowiki>!
# If You work on it, and You think it will make to next release, '''MOVE''' to  ''[[#In progress]]'' section.
# 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.
# 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 freaze end. Only bugfixes and commits related to items listed in ''In progress'' section.
'''''Warning''''' After [[GRASS_6.3_release_schedule|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 ===
=== TODO ===

Revision as of 10:03, 4 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:

  1. 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 ~~~~!
  2. If You work on it, and You think it will make to next release, MOVE to #In progress section.
  3. 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

  • Create 3D animation w nviz showing GRASS 3D coolness. MarisN 12:00, 4 August 2006 (CEST)

In progress

Finished