[GRASS5] GRASS 6.0.1 release schedule

[Maciek Sieczka]

From: "Hamish" <hamish_nospam at yahoo.com>

>> I think that it's time to get out GRASS 6.0.1 bugfix release.
>> The 6.0.1 version should be in a good shape now.
>>
>> Here a proposed schedule:
>
> Sounds good.
>
>
>
> To recall a bug list from a previous email:
>
> --
> Subject: [GRASS5] Re: [Pkg-grass-general] update
> Date: 2005-05-28 01:01:57 GMT
> I wrote:
>
>> [Pkg-grass-general]
>> > > GRASS 6.0.1 has not been released yet.
>> >
>> > So we should do that!
>>
>>
>> critical bugs to fix:
>>
>> cs2cs doesn't see GRASS's NTv2 grid files. see:
>>   http://bugzilla.remotesensing.org/show_bug.cgi?id=834
>
> Fixed by Paul. I have lightly tested; don't know if it has been applied
> to the 6.0.x release branch.
>
>
>> v.in.garmin - add more checks to survive above bug when downloading
>> track.
>
> done. Merged.
>
>
>> r.out.gdal - broken with quoting problem.
>
> done. I don't know if it has been applied to the 6.0.x release branch.
>
>
>> r.terraflow still using insecure temp files
>
> Laura pointed out that r.terraflow uses mkstemp() to create the temp
> files in raster/r.terraflow/IOStream/lib/src/ami_stream.cc. So the temp
> files should be secure after all.
>
>
>> 100% cpu usage during mouse ops. Real problem for multi-user machines
>> and when using GRASS over a network connection.
>
> outstanding, not good, but not release critical.
>
>
> others?
>
>
> Hamish

Several. Not sure if really none of them has been fixed - I've been using a 
month old 6.1 CVS and can't grab a fresh one right now (modem). Besides, 
none of the comments in the bugtracker proves any has been fixed thus it 
would be good to take a look at them and evantually close. Other bug reports 
of mine which I'm sure got fixed I closed about a month ago. I might be able 
to test these remaining bugs with a fresh 6.1 CVS about next weekend. Plaese 
do it yourself if you can't wait.

r.proj works ONLY when source and target mapset names are identical
http://intevation.de/rt/webrt?serial_num=3362&display=History

d.where -l is giving wrong results
http://intevation.de/rt/webrt?serial_num=3172&display=History
(Paul said it shouldn't be hard to fix yet the discussion stopped at some
point. Quite important - GIS should handle any coordinates conversion 
perfect.)

zooming in v.digit changes resolution in region settings
http://intevation.de/rt/webrt?serial_num=2962&display=History

if you zoom in/out much v.digit is likely to crash
http://intevation.de/rt/webrt?serial_num=3047&display=History
(I guess that http://intevation.de/rt/webrt?serial_num=3164&display=History
refers to the same problem.)

r.to.vect - broken pipe
http://intevation.de/rt/webrt?serial_num=3168&display=History
(Guessing - might it be related to problems with topology support for points 
and memory leaks with v.in.ascii which were dicussed recenlty on grass devel 
list?)

r.statistics G_calloc: out of memory
http://intevation.de/rt/webrt?serial_num=2668&display=History
(Sorry, I haven't checked if it applies in 6.0/6.1; could somebody do it?)

invisible errors in GUI
http://intevation.de/rt/webrt?serial_num=3010&display=History
(If a segfault happens when the command is called from GUI there is *no any
information* for the user about it, all looks normal. Thus, one can seat for
ages and wonder, why the program doesn't make any progress).

v.type GUI bug
http://intevation.de/rt/webrt?serial_num=2969&display=History

v.in.ogr, GUI, fails during "Building areas:"
http://intevation.de/rt/webrt?serial_num=2937&display=History
(As far as I recall Radim told me it doesn't make sense to fix this bug 
because TCL/TK interface "has no future". Maybe right, but a bug is a bug.)

r.bilinear result is rounded to .5, GUI and --help issues
http://intevation.de/rt/webrt?serial_num=2790&display=History
(The "rounded to 0.5" issue still aplies as I recall.)

r.info displays the '(zone 0)' message in any location
http://intevation.de/rt/webrt?serial_num=3054&display=History
(A lot mess there, sorry! Go to the bottom of the page, there is a fresh
comment by me).

r.mapcalc - warning/errorr amibiguity
http://intevation.de/rt/webrt?serial_num=3069&display=History

d.m should close on exit
http://intevation.de/rt/webrt?serial_num=3050&display=History

v.to.rast doesn't asign the cats and labels
http://intevation.de/rt/webrt?serial_num=3045&display=History

I'm talking here of my bugs. Could other reporters take a look at their bugs 
as well? I mean if 6.0.1 is really going to be a bugfix relaese...

Cheers
Maciek