[GRASS5] features needed for 6.2

[Markus Neteler]

On Wed, Mar 29, 2006 at 07:49:32PM +1200, Hamish wrote:
> Ok, trying to combine everyone's comments into a draft plan/roadmap:
> 
> We release 6.0.3 whenever it feels right, independent of 6.1+.

Yes, we can even do this soon as I have backported two
relevant changes (NVIZ tcltk8.4 support and fftw3)
 
...
> Consensus is to include GEM and gis.m in 6.2.0. It would be nice to have
> them both in raw form in the 6.1.0 development snapshot release, but
> they don't have to be perfect for that.

Benjamin, what's the state?
 
...
> SQLite as default db: I think SQLite support is still too young and
> lightly tested, and it is too important that it doesn't have problems.
> Also I don't like the extra dependency.

SQLite is getting fairly standard these days. Also QGIS needs it.
We can just invite people to use GRASS-SQLite to find out if it
works or not. I do so since I find DBF pretty limited.

> If consensus is that this should
> happen at some point, I suggest it does in CVS in the *days after* 6.2.0
> is released. But this is a catch-22 situation.. to get tested it needs
> to be default, so if consensus is that it should be default for 6.2.0, I
> think we need to make it the default ASAP.
> 
> New startup GUI: if it is ready by 8 weeks after 6.1.0 it can be in
> 6.2.0. Otherwise add it after.
> 
> GUIs for r.digit*, i.points: If ready in the 4 weeks after 6.1.0 is
> released put it in for 6.2.0. If after that then wait until after 6.2.0.
> i.e. We shouldn't wait for it to mature before we can release 6.2.
> Same for a GUI frontend to g.gisenv and gis.m preferences.
> [*] I take it you meant r.digit and not v.digit Michael?

Not related to GUI, but related to a new i.points (as long time
promised):

http://mpa.itc.it/markus/tmp/i.points.auto_30_mar_2006.tar.gz

This should be the merge of i.points + i.vpoints along with
homography support (geocoding by lines instead of points which is
much easier/faster) and auto-GPC search (based on Fourier correlation).
There is a file HANDBOOK inside which explains it a bit. Today
I found some raster-map negative row bug, maybe someone wants to give it
a try? Would be fun to have that in GRASS soon.

...
> If he is happy to do so, I hope Markus will remain as release manager
> and generally as the arbitrator in charge of final decisions.

Yes, I can give a hand of course.
 
> I feel really good about where 6.1-cvs is right now; 64bit & large file
> bugs are still trickling in (as expected), but otherwise things are
> pretty strong.

Well, 64bit is doing pretty well AFAIK (only 64bit machines in the office
now). Large file is causing problems, Glynn had commented on this but
then the issue disappeared. Maybe his grass-header-fix script could also
do the config.h trick which he suggested?

Markus