[GRASS-dev] GRASS GIS 6.4.3RC2 released

Helena Mitasova hmitaso at ncsu.edu
Sat Feb 2 16:30:23 PST 2013


On Feb 2, 2013, at 6:36 PM, Helmut Kudrnovsky wrote:

>> A second release candidate of GRASS GIS 6.4.3 is now available. 
> 
> since it's more than a month ago now, what about another another RC or
> release?
> 
> maybe anything for the community sprint next week?

Excellent suggestion. There is a number of unresolved issues, but hopefully not too difficult to fix:

- r3.in.ascii broken handling of input parameters (it runs only with defaults, if you need to change something,
e.g. specify * for nulls it gives error - more details here
http://trac.osgeo.org/grass/ticket/1801

- the isosurfaces now work on macosx10.8 with changes made by Michael - this needs to be further tested and
done for GRASS6.4.3 as well - Michael, can you put your solution into bug report #1736 and then
if it works perhaps this can be closed (btw I found #803 with isosurfaces crashing on linux with segfault -
I am wondering whether this was related).

-wxnviz - in wxnviz for draped vector lines after I change the line width e.g. to 0,
the displayed line goes back to wider line each time something else is drawn
(e.g. fringe or view is changed) but the number is still set to 0.  (I haven't submitted a bug report on this yet)


There are numerous other tickets which I am not sure how important it is to have them fixed  -
e.g. 
#1837 d.rast.edit
#1820 multiple map displays
#1797 r.li.padcv
#1787 profile tool on mac - may be fixed already, I can test
#1784 r3.info and g.region rast3d in wingrass - still an issue? needs to be tested and fixed if still broken
and many others
also, several gui modeler issues (this can be considered as prototype module? )
and d.legend run in command console does not carry over the parameters, d.legend panel sometimes
opens behind the display window leading to user confusion

Not really a bug, but there are various error messages on Windows and Mac that don't seem to cause any problems
except for user confusion - I am not sure how important it is to take care of them - if it is something that 
should be fixed I can collect the info and post here (or submit bug report?)

It would be great to use the code sprint to make some progress on the release of GRASS6.4.3,

Helena

> 
> 
> 
> 
> 
> -----
> best regards
> Helmut
> --
> View this message in context: http://osgeo-org.1560.n6.nabble.com/GRASS-GIS-6-4-3RC2-released-tp5024186p5031708.html
> Sent from the Grass - Dev mailing list archive at Nabble.com.
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev



More information about the grass-dev mailing list