[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.
> ..
>> > To recall a bug list from a previous email:
> ..
>> >> critical bugs to fix:
> ..
>> > others?
> ..
>> Several.
>
> Of course there are many unfixed bugs that are important to individual
> users,

Oh no, I didn't write this all that just to satisfy my needs.

I don't use v.digit (almost) because it's risky, "d.where -l" bug is not a 
big problem for me because I know about it and since then do't use it, 
similar with "invisible errors in GUI", "v.type GUI bug", "v.in.ogr, GUI, 
fails during "Building areas:" etc..

Maybe only the "r.to.vect - broken pipe" might show out a work-stopper for 
me when day when I really need to convert few 3" SRTMs to vector points for 
reprojection and re-interpolation.

So I'm writing about this all to get hopefully fixed and to spare other 
folks same troubles, first of all. Yes, I can't fix it myself so I realise I 
might be bothering talking of them over and over again. And I'm very 
gratefull for all those you mighty coders fixed, which helped us all to use 
Grass more efficiently and easier.

On the other hand, it is hard for me to advertise Grass to others when I 
know there are bugs in such an important module as v.digit. Or that if he 
uses GUI and segfault appears he won't even know about it and will meaybe 
say instead "Well, I'll leave the computer on till tomorrow and see what 
happens". Or that "d.where -l" will give him wrong coordinates, (sick!).

> I was mostly refering to severe release critical bugs that we
> should not release a new version without fixing first.

Few of those I mention are critical, aren't they?

> There can always
> be a 6.0.2 release

BTW - will there be 5.4.1? I know you are not in charge but could the one 
please answer?

> with more bug fixes sometime in the future, but don't
> hold up the current release to fix every single bug in the software,
> otherwise it will never happen.
I'm not holding anything because. I'm asking you Guys to fix those critical 
bugs before releasing bug-fix release. Sorry if you can't.

Here's what I imagine: Say I started using Grass from 6.0. Then 6.0.1 - 
great bug-fix release! And what? Same old bugs remain. In spite of the fact 
they have been know for several weeks or months. I wonder what I would have 
thought of GRASS.

>> 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).
>
>
> cd grass61-source
> make distclean
> cvs login
> cvs -z3 update -dP

OK, that was a poor excuse ;). I will need to learn how to use CVS soon 
anyway. Thanks for the example. And I hope I can find enough time next 
weekend to test all the bugs I have reported so far which haven't got 
officialy fixed.

Maciek