[GRASS-dev] GRASS 7.0beta3 planning

neteler · May 25, 2014, 9:23pm

Hi,

as Martin stated in a recent ticket comment, beta3 should be released asap.

I would like to get first the pygrass changes backported (not
difficult including the manual improvements).
A few more things are potentially missing, too.

Opinions?

Markus

annakrat · May 25, 2014, 10:41pm

On Sun, May 25, 2014 at 5:23 PM, Markus Neteler <neteler@osgeo.org> wrote:

Hi,

as Martin stated in a recent ticket comment, beta3 should be released asap.

I would like to get first the pygrass changes backported (not
difficult including the manual improvements).
A few more things are potentially missing, too.

I backported what I think is appropriate and these (not critical) tickets
are still waiting for confirmation:

http://trac.osgeo.org/grass/ticket/2243

this needs more testing across platforms, both with wxPython 2.8 and 3, so
we might want to wait
http://trac.osgeo.org/grass/ticket/2026 (v.surf.rst window too wide)

Anna

Opinions?

Markus
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

lucadelu · May 26, 2014, 9:03am

On 25 May 2014 23:23, Markus Neteler <neteler@osgeo.org> wrote:

Hi,

Hi,

as Martin stated in a recent ticket comment, beta3 should be released asap.

I would like to get first the pygrass changes backported (not
difficult including the manual improvements).

Today and tomorrow I would like to improve a little bit more the
pygrass manual, could you wait few days before backport these changes?

A few more things are potentially missing, too.

Opinions?

Markus

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org

neteler · June 6, 2014, 7:41pm

On Sun, May 25, 2014 at 11:23 PM, Markus Neteler <neteler@osgeo.org> wrote:

Hi,

as Martin stated in a recent ticket comment, beta3 should be released asap.

I would like to get first the pygrass changes backported (not
difficult including the manual improvements).

Maybe we skip the pygrass sphinx docs for RC3?
... the OSGeoLive feature freeze for the FOSS4G Portland conf is upcoming.

But other pygrass fixes should be backported.

Markus

wenzeslaus · June 6, 2014, 7:52pm

On Fri, Jun 6, 2014 at 3:41 PM, Markus Neteler <neteler@osgeo.org> wrote:

Maybe we skip the pygrass sphinx docs for RC3?

Anyway we mostly focus on the online documentation being up to date, right?

... the OSGeoLive feature freeze for the FOSS4G Portland conf is upcoming.

This would be nice.

neteler · June 7, 2014, 11:21pm

Hi,

here a list of backport candidates:

r60692 v.out.ogr
r60674 v.in.ogr
r60656 v.in.ogr
r60596 v.in.ogr
r60595 v.in.ogr
r60662 lib/python/script/raster.py

# needed for QGIS
r60590 include/defs/gis.h, lib/gis/error.c

please comment or backport,
Markus

martinl · June 8, 2014, 9:07am

Hi,

2014-06-08 1:21 GMT+02:00 Markus Neteler <neteler@osgeo.org>:

I went through my list of planned backports and did the job
(r60736-44). The rest I will leave for authors of mentioned commits
(hcho and annakrat).

Martin

--
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa

Huidae_Cho · June 8, 2014, 10:08am

I merged the v.in/out.ogr backports except r60596 because v.in.ogr in relbr7 doesn’t have the PG specific code, which I wasn’t sure can be simply copied over from trunk… Martin?

···

On Sun, Jun 8, 2014 at 5:07 AM, Martin Landa <landa.martin@gmail.com> wrote:

Hi,

2014-06-08 1:21 GMT+02:00 Markus Neteler <neteler@osgeo.org>:

I went through my list of planned backports and did the job
(r60736-44). The rest I will leave for authors of mentioned commits
(hcho and annakrat).

Martin

–
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa

grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

martinl · June 8, 2014, 10:40am

Hi,

2014-06-08 12:08 GMT+02:00 Huidae Cho <grass4u@gmail.com>:

I merged the v.in/out.ogr backports except r60596 because v.in.ogr in relbr7
doesn't have the PG specific code, which I wasn't sure can be simply copied
over from trunk... Martin?

it's related to PG database/ogr driver, seems to be OK.

Martin

--
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa

Huidae_Cho · June 8, 2014, 10:50am

Done in r60748.

···

On Sun, Jun 8, 2014 at 6:40 AM, Martin Landa <landa.martin@gmail.com> wrote:

Hi,

2014-06-08 12:08 GMT+02:00 Huidae Cho <grass4u@gmail.com>:

I merged the v.in/out.ogr backports except r60596 because v.in.ogr in relbr7
doesn’t have the PG specific code, which I wasn’t sure can be simply copied
over from trunk… Martin?

it’s related to PG database/ogr driver, seems to be OK.

Martin

–
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa

wenzeslaus · July 17, 2014, 10:22pm

Hi,

what do you think about releasing beta3? The problems mentioned in this thread were fixed and fixes backported except for r60590 which is safe for GRASS by itself and thus can be safely backported now.

Vaclav

r60590
Add G_fatal_longjmp() (needed for QGIS)
glynn
include/defs/gis.h, lib/gis/error.c
http://trac.osgeo.org/grass/changeset/60590

There is a lot of things in the tracker but they can be postponed I think:

long-term problem for non-ascii languages
http://trac.osgeo.org/grass/ticket/1681

remove ffmpeg from libogsf and configure.in
let’s do it in trunk first, it does not have to be in beta
http://trac.osgeo.org/grass/ticket/2017

wxGUI vector digitizer passing unescaped text to database
security issue but not a real issue for most of the users I guess
http://trac.osgeo.org/grass/ticket/2252

missing documentation

bad but does not stop beta release
http://trac.osgeo.org/grass/ticket/2259

inconsistent random number generation
long-term problem, beta can live with it
http://trac.osgeo.org/grass/ticket/2272

insufficient error message when addons are mixed on MS Windows
To be honest, I’m not sure why this is a blocker
http://trac.osgeo.org/grass/ticket/2283

rename some imagery modules
should be done before release but not needed for beta
http://trac.osgeo.org/grass/ticket/2340

I’m not really familiar with these
http://trac.osgeo.org/grass/ticket/995
http://trac.osgeo.org/grass/ticket/1891

Python and MS Windows
there is a solution in 7.0 and some advances were made also in trunk
http://trac.osgeo.org/grass/ticket/580
http://trac.osgeo.org/grass/ticket/1871
http://trac.osgeo.org/grass/ticket/2150

hellik · July 18, 2014, 6:39am

what do you think about releasing beta3?

have look in
http://lists.osgeo.org/pipermail/grass-dev/2014-July/069983.html

"[GRASS-dev] GRASS 7: g.gui.rlisetup

[...]
Backport of r60219 is needed.
http://trac.osgeo.org/grass/changeset/60219"

g.gui.rlisetup isn't starting in winGRASS7.0

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/GRASS-7-0beta3-planning-tp5142434p5151655.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

neteler · July 21, 2014, 9:21pm

On Fri, Jul 18, 2014 at 8:39 AM, Helmut Kudrnovsky <hellik@web.de> wrote:

what do you think about releasing beta3?

have look in
http://lists.osgeo.org/pipermail/grass-dev/2014-July/069983.html

"[GRASS-dev] GRASS 7: g.gui.rlisetup

[...]
Backport of r60219 is needed.
http://trac.osgeo.org/grass/changeset/60219"

Done in r61304.

g.gui.rlisetup isn't starting in winGRASS7.0

Please test tomorrow's binary snapshot.

Markus

neteler · July 21, 2014, 9:23pm

On Fri, Jul 18, 2014 at 12:22 AM, Vaclav Petras <wenzeslaus@gmail.com> wrote:

what do you think about releasing beta3?

Yes and no: it is time to do it but without the current blocker.

The problems mentioned in this
thread were fixed and fixes backported except for r60590 which is safe for
GRASS by itself and thus can be safely backported now.

...

r60590
Add G_fatal_longjmp() (needed for QGIS)
glynn
include/defs/gis.h, lib/gis/error.c
http://trac.osgeo.org/grass/changeset/60590

... if so, please do (someone) that.

There is a lot of things in the tracker but they can be postponed I think:

It is important to make real issues either blocker or at least
critical to avoid that it slips through.

... I think we need to shift this listing either to a Wiki or to trac
bugs. It is not efficient to do it via email (let's use that for the
ping'ing).

Concerning the BAT file support, is that now in relbr7?

Markus

wenzeslaus · July 21, 2014, 10:32pm

On Mon, Jul 21, 2014 at 5:23 PM, Markus Neteler <neteler@osgeo.org> wrote:

On Fri, Jul 18, 2014 at 12:22 AM, Vaclav Petras <wenzeslaus@gmail.com>
wrote:
> what do you think about releasing beta3?

Yes and no: it is time to do it but without the current blocker.

There is currently 10 blockers for 7.0 and 7.1, 3-5 are duplicates of

Python issue.

In addition to that. The g.list, g.mlist, g.remove and g.mremove chnages
are in fact blockers since they are changing API.

There is a lot of things in the tracker but they can be postponed I think:

It is important to make real issues either blocker or at least

critical to avoid that it slips through.

... I think we need to shift this listing either to a Wiki or to trac
bugs. It is not efficient to do it via email (let's use that for the
ping'ing).

The query on Trac seems appropriate. We can add it to reports (as what?)

or you can put a query result to a page. Some pages are using it.

== List of tickets ==

[[TicketQuery(component=wxGUI&keywords=wxiclass&order=priority)]]

http://trac.osgeo.org/grass/wiki/wxGUIDevelopment/wxIClass#Listoftickets

http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=milestone&col=status&col=type&col=priority&col=component&col=version&col=keywords&col=time&col=changetime&milestone=7.0.0&type=!enhancement

Concerning the BAT file support, is that now in relbr7?

No, relbr7 is using the older workaround. And about BAT and Python in

general in trunk. I'm now confused about what was implemented and why.

Vaclav

Markus

hellik · July 22, 2014, 9:57am

Markus Neteler wrote

On Fri, Jul 18, 2014 at 8:39 AM, Helmut Kudrnovsky <

hellik@

> wrote:

what do you think about releasing beta3?

have look in
http://lists.osgeo.org/pipermail/grass-dev/2014-July/069983.html

"[GRASS-dev] GRASS 7: g.gui.rlisetup

[...]
Backport of r60219 is needed.
http://trac.osgeo.org/grass/changeset/60219"

Done in r61304.

g.gui.rlisetup isn't starting in winGRASS7.0

Please test tomorrow's binary snapshot.

Markus
_______________________________________________
grass-dev mailing list

grass-dev@.osgeo

http://lists.osgeo.org/mailman/listinfo/grass-dev

tested with:

GRASS Version: 7.0.0svn
GRASS SVN Revision: 61304
Erstellungsdatum: 2014-07-22
Build Platform: i686-pc-mingw32
GDAL/OGR: 1.11.0
PROJ.4: 4.8.0
GEOS: 3.4.2
SQLite: 3.7.17
Python: 2.7.4
wxPython: 2.8.12.1
Platform: Windows-Vista-6.0.6002-SP2 (OSGeo4W)

g.gui.rlisetup is working now; but an g.gui.rlisetup-entry in the main GUI
is missing.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/GRASS-7-0beta3-planning-tp5142434p5152402.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

annakrat · July 22, 2014, 1:47pm

On Tue, Jul 22, 2014 at 5:57 AM, Helmut Kudrnovsky <hellik@web.de> wrote:

Markus Neteler wrote
> On Fri, Jul 18, 2014 at 8:39 AM, Helmut Kudrnovsky <

> hellik@

> > wrote:
>>> what do you think about releasing beta3?
>>
>> have look in
>> http://lists.osgeo.org/pipermail/grass-dev/2014-July/069983.html
>>
>> "[GRASS-dev] GRASS 7: g.gui.rlisetup
>>
>> [...]
>> Backport of r60219 is needed.
>> http://trac.osgeo.org/grass/changeset/60219"
>
> Done in r61304.
>
>> g.gui.rlisetup isn't starting in winGRASS7.0
>
> Please test tomorrow's binary snapshot.
>
> Markus
> _______________________________________________
> grass-dev mailing list

> grass-dev@.osgeo

> http://lists.osgeo.org/mailman/listinfo/grass-dev

tested with:

GRASS Version: 7.0.0svn
GRASS SVN Revision: 61304
Erstellungsdatum: 2014-07-22
Build Platform: i686-pc-mingw32
GDAL/OGR: 1.11.0
PROJ.4: 4.8.0
GEOS: 3.4.2
SQLite: 3.7.17
Python: 2.7.4
wxPython: 2.8.12.1
Platform: Windows-Vista-6.0.6002-SP2 (OSGeo4W)

g.gui.rlisetup is working now; but an g.gui.rlisetup-entry in the main GUI
is missing.

Isn't it the 'Set up sampling and analysis framework? ' in Raster ->
Landscape patch analysis?

Anna

-----
best regards
Helmut
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/GRASS-7-0beta3-planning-tp5142434p5152402.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

hellik · July 22, 2014, 2:14pm

Anna Petrášová wrote

g.gui.rlisetup is working now; but an g.gui.rlisetup-entry in the main
GUI
is missing.

Isn't it the 'Set up sampling and analysis framework? ' in Raster ->
Landscape patch analysis?

Anna

ah, yes, you're right, sorry for the noise.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/GRASS-7-0beta3-planning-tp5142434p5152495.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

neteler · July 22, 2014, 8:36pm

On Mon, May 26, 2014 at 11:03 AM, Luca Delucchi <lucadeluge@gmail.com> wrote:

On 25 May 2014 23:23, Markus Neteler <neteler@osgeo.org> wrote:
> as Martin stated in a recent ticket comment, beta3 should be released asap.
>
> I would like to get first the pygrass changes backported (not
> difficult including the manual improvements).

Today and tomorrow I would like to improve a little bit more the
pygrass manual, could you wait few days before backport these changes?

all:
I guess we are completely out of sync concerning the PyGRASS docs.
(Un)related to beta3, how should we handle that? Backport it after beta3?

Markus

lucadelu · July 23, 2014, 7:56am

On 22 July 2014 22:36, Markus Neteler <neteler@osgeo.org> wrote:

all:
I guess we are completely out of sync concerning the PyGRASS docs.
(Un)related to beta3, how should we handle that? Backport it after beta3?

I think it is better...we could move PyGRASS, WXGUI and Python script
documentation for the next beta or for the first RC.

Markus

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org