Re: [GRASS-dev] [GRASS-PSC] RFC4 discussion call

2015-01-07 Thread Helena Mitasova
On Jan 7, 2015, at 4:20 PM, Markus Neteler wrote: > On Wed, Jan 7, 2015 at 9:26 AM, Massimiliano Cannata > wrote: >> Dear all, I went trough the document and it make perfectly sense to me. > > I agree. I updated its date now and expanded "RC" in the beginning. > > http://trac.osgeo.org/grass/w

Re: [GRASS-dev] [GRASS-PSC] RFC4 discussion call

2015-01-07 Thread Margherita Di Leo
Hi, I read the document and support it, On Wed, Jan 7, 2015 at 10:20 PM, Markus Neteler wrote: > > > Last doubts: > > * Step1: "The Project manager (or if exists the Release manager) > then collects reactions to decide whether there is sufficient support > for this proposal. " > > --> this

Re: [GRASS-dev] [GRASS-PSC] RFC4 discussion call

2015-01-07 Thread Markus Neteler
On Wed, Jan 7, 2015 at 9:26 AM, Massimiliano Cannata wrote: > Dear all, I went trough the document and it make perfectly sense to me. I agree. I updated its date now and expanded "RC" in the beginning. http://trac.osgeo.org/grass/wiki/RFC/4_ReleaseProcedure Last doubts: * Step1: "The Proj

Re: [GRASS-dev] [GRASS-PSC] RFC4 discussion call

2015-01-07 Thread Markus Neteler
On Tue, Jan 6, 2015 at 11:25 AM, Martin Landa wrote: > I would also agree with that. It would be reasonable also to set some > deadline for discussion and then to propose voting. What do you think? For this RFC? Yes. But I think we are pretty close now. > I did cosmetics changes [1]. > [1] > htt

Re: [GRASS-dev] Is grass70b4 compiling on FreeBSD ?

2015-01-07 Thread Glynn Clements
Fábio Dias wrote: > The files /usr/include/iconv.h and /usr/local/include/iconv.h are different. Does /usr/include/iconv.h contain the macros? #define iconv_open libiconv_open #define iconv libiconv #define iconv_close libiconv_close If not, it looks like it's now picki

Re: [GRASS-dev] Tests down to 78% (from 84%), mostly PyGRASS

2015-01-07 Thread Pietro
Hi Vaclav, Il 07/gen/2015 16:11 "Vaclav Petras" wrote: > Thanks but the tests are failing with different error now: > > > Traceback (most recent call last): > File "lib/python/pygrass/raster/testsuite/test_raster.py", line 6, in > from grass.pygrass.raster import RasterRow > File "etc/py

Re: [GRASS-dev] Tests down to 78% (from 84%), mostly PyGRASS

2015-01-07 Thread Vaclav Petras
On Mon, Jan 5, 2015 at 4:15 PM, Martin Landa wrote: > 2015-01-05 21:21 GMT+01:00 Markus Neteler : > > No problem. The only remaining thing which I don't understand how to > > fix it is this: > > > > File "./lib/gis/testsuite/gis_lib_env_test.py", line 31, in test_gisrc > > libgis.G__read_gi

Re: [GRASS-dev] compile gdal with grass

2015-01-07 Thread Paulo van Breugel
Hi Martin, just recompiled GDAL against GRASS, and I can confirm it works. Thanks for the fix! On Mon, Jan 5, 2015 at 3:50 PM, Martin Landa wrote: > Hi, > > 2015-01-05 15:32 GMT+01:00 Markus Neteler : > > On Mon, Jan 5, 2015 at 12:56 PM, Martin Landa > wrote: > > ... > >> these errors are rela

Re: [GRASS-dev] point cloud analysis: new features

2015-01-07 Thread Paulo van Breugel
On Mon, Jan 5, 2015 at 12:17 PM, Benjamin Ducke wrote: > On 04/01/15 23:00, Paulo van Breugel wrote: > > Tried it out, and it works like a charm, great! > > > > One question/request, would it be terribly difficult to add an option to > > compute an user-defined number of clusters of equal size? >

Re: [GRASS-dev] [GRASS GIS] #2522: d.vect.thematic, d.thematic.area in GRASS 7.0

2015-01-07 Thread GRASS GIS
#2522: d.vect.thematic, d.thematic.area in GRASS 7.0 --+- Reporter: martinl | Owner: grass-dev@… Type: defect| Status: new

Re: [GRASS-dev] [GRASS GIS] #2440: remove unused elements from g.list/g.remove

2015-01-07 Thread GRASS GIS
#2440: remove unused elements from g.list/g.remove +--- Reporter: annakrat| Owner: grass-dev@… Type: task| Status: new Priority: blocker

Re: [GRASS-dev] [GRASS-PSC] RFC4 discussion call

2015-01-07 Thread Massimiliano Cannata
Dear all, I went trough the document and it make perfectly sense to me. Just a minor comment is that we shall probably clearly specify who is responsible for the mentioned actions: call for soft, hard freeze etc. Basically who is responsible to recall all to the respect of the mentioned time-frame