[GRASS5] Re: GRASS 5.1 startup/grass5.0 release

[Helena Mitasova]

Glynn, Eric, and others who have the most recent CVS version
would you be so kind and give Markus some feedback whether he could
release the current GRASS5.0 as a stable, final release ? (see our discussion
below). My major argument is that people are dowloading and using
GRASS4.3 as a current stable version, while I believe that GRASS5.0
as it is now is just plain much better and people should be using it,
(in spite of all the enhancements and fixes that it still needs.)

thanks for your input,

Helena

Markus Neteler wrote:

> Helena,
>
> On Wed, Oct 10, 2001 at 09:35:55AM -0400, Helena Mitasova wrote:
> > >
> > > >
> > > > BTW, what's left to do before 5.0 can be "released"?
> > >
> > > see my other mail:
> > >
> > >  - NVIZ TOP button needs a fix, NVIZ is really behaving strange here
> > >    (Bob already spend a lot of time on that)
> >
> > Markus, if it cannot be fixed in 1 hour, then remove it and go back to the
> > previous version.
> > After Bob has fixed the disappearing surface and lights NVIZ worked really
> > well.
>
> the TOP button doesn't break anything and only sometimes fails in the
> following way: You always get a top view, but somtimes the map is
> rotated (north to east or south). TOP is always top, but not always
> the "north-up" view which is mostly expected. But that's really not
> severe (so I suggest to keep this useful button) since the
> user can easily rotate the map using the puck.
>
> > The release of GRASS5.0 should not be hold on this. I believe, that at
> > this stage such enhancements really should not be added, because GRASS
> > will never get released.
>
> Yes, I agree (and I am a bit tired of 5.0.0).
>
> > >
> > >  - r.in.gdal: fix the currently hard_coded LL "projection" for
> > >    GCPs (means: fix the wkt_to_grass()
> > >  - Huidae is currently adding cats transfer to r.mapcalc for
> > >    the two cases:
> > >     new_mapname = oldmapname
> > >     new_mapname = if(cond, old_mapname1, old_mapname2)
> > >  - Andrea Aime and me are finishing the cats support for s.delaunay
> > >    (have been missing, which lead to broken polygons)
> > >  - more?
> >
> > overall, I believe, that long time ago, only the absolutely essential bug fixes
> > should have been holding GRASS release and non essential features
> > and enhancements should be left for the next release or as patches that people
> > can download separately. It appears to me that each time the GRASS5pre* is
> > released
> > the list of TODO things gets longer rather than shorter.
> > There are many people sticking to a totally obsolete GRASS4.3 - which is listed
> > on the web site as current,stable version instead of using GRASS5.0 which I
> > believe
> > has probably fewer bugs, is easier to install and has incomparably improved
> > capabilities.
> > We all know that there is about a milion improvements and fixes needed for
> > GRASS,
> > but it runs pretty well as it is and it is definitely suitable for routine,
> > everyday production
> > work so I think that you should cut-off any new development and enhancements
> > and release it. GRASS has been really imporved tremendously, that you all for
> > that,
> > and it is a shame that many users are still having to use GRASS4.3
>
> I agree 100%. Perhaps you post this on "grass5" as well? If nobody
> minds, we can release stable today... I am open for this idea.
>
> Best regards
>
>  Markus
>
> PS: as suggested, I have changed
>  GRASS 5.0.0pre2 [current pre]
>  GRASS 4.3 [old stable]
>  here: http://grass.itc.it/index2.html