[GRASS5] Code Freeze schedule

[Markus Neteler]

Hi all,

after receiving another request for code freeze to finalize
the GRASS 5 stable I want to propose a schedule (with your 
assistance):

Things which should go into GRASS 5.0 stable
 - new "init" mechanism (Justin Hickey)
 - new env variable management (Justin Hickey)
 - new autoconf (Eric Mitchell)
 - Datum support for projections (Andreas Lange)
 - sockets Xdriver (Carl Anderson)
 - extent the test-suite testgrass.sh (all)

 -> is this realistic?: please correct me, if not

Things which should go into GRASS 5.1 development
 - code restructuring to packages (requires autoconf)
 - 3D vectors (David D Gray, Radim Blazek)
 - probably replace GRASS i/o routines by "libgrass" (Frank Warmerdam)
 - layered XDRIVER (Pierre de Mouveaux)
 - full RGB support in all display modules (Pierre de Mouveaux)
 - tons of other stuff


Timeline:
 - 1. Oct. 2000: Code freeze, split into stable tree and development tree
 
 - start bugfixing only on stable tree, *concentrate* on bugfixes
 - exeptional continue meanwhile on development team
 
 - xx.xx.2000: Publish GRASS 5.0stable


What's missing? Any other suggestions? Is code freeze at Oct. 1 too
early/late?

Awaiting your comments

 Markus

-- 
Dipl.-Geogr. Markus Neteler *  University of Hannover
Institute of Physical Geography and Landscape Ecology
Schneiderberg 50 * D-30167 Hannover * Germany
Tel: ++49-(0)511-762-4494  Fax: -3984

---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'