[GRASS-dev] pygrass vector changes and backport planning (7.0.x? or 7.1.x?)

GRASS GIS GRASS GIS developer
1

Dear Markus and Sören, dear devs,

Thanks to Sören's work the pygrass vector library has been improved a
lot in trunk during the last weeks. So far they are not signed to be
backported [0].
I would like to understand when do you think these changes can be
ported to the stable branch and in which stable (7.0.X or 7.1.X)
relaease?
Which one will be more appropriate?
When do you think the next stable will be? :slight_smile:

I would avoid to let the two branches differ too much, and I think we
should try to make trunk as much close to the release candidate as
possible if the changes seem to work.

I'm thinking when should I start updating all the r.green modules.

If you think that these changes should be ported to 7.1.X then probaly
I need a grass71 directory in grass_addons...

Let me know.

Pietro

[0] https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.0.2tobebackported

2

Hi,

2015-10-09 15:25 GMT+02:00 Pietro <peter.zamb@gmail.com>:

Thanks to Sören's work the pygrass vector library has been improved a
lot in trunk during the last weeks. So far they are not signed to be
backported [0].

I would suggest to mark them to backported for 7.0.3 (ideally when
7.0.2 will be out).

I would like to understand when do you think these changes can be
ported to the stable branch and in which stable (7.0.X or 7.1.X)
relaease?

When do you think the next stable will be? :slight_smile:

7.0.2 as soon as possible (@Markus: what about next week?)

I would avoid to let the two branches differ too much, and I think we
should try to make trunk as much close to the release candidate as
possible if the changes seem to work.

I would suggest to avoid heavy backporting to relbr70 (let's stay here
with backports and minor changes). I would suggest to start preparing
trunk to be switched to relbr_71 instead. Something like:

* january 2016 (trunk -> relbr_71)
* march 2016 - release 7.1

Make sense to you?

If you think that these changes should be ported to 7.1.X then probaly
I need a grass71 directory in grass_addons...

Maybe you could modify your modules to detect if user is running 7.0
or 7.1? Martin

3

On Fri, Oct 9, 2015 at 3:37 PM, Martin Landa <landa.martin@gmail.com> wrote:

Hi,

2015-10-09 15:25 GMT+02:00 Pietro <peter.zamb@gmail.com>:

Thanks to Sören's work the pygrass vector library has been improved a
lot in trunk during the last weeks. So far they are not signed to be
backported [0].

I would suggest to mark them to backported for 7.0.3 (ideally when
7.0.2 will be out).

I would like to understand when do you think these changes can be
ported to the stable branch and in which stable (7.0.X or 7.1.X)
relaease?

When do you think the next stable will be? :slight_smile:

7.0.2 as soon as possible (@Markus: what about next week?)

yes, please.

I would avoid to let the two branches differ too much, and I think we
should try to make trunk as much close to the release candidate as
possible if the changes seem to work.

I would suggest to avoid heavy backporting to relbr70 (let's stay here
with backports and minor changes). I would suggest to start preparing
trunk to be switched to relbr_71 instead. Something like:

* january 2016 (trunk -> relbr_71)
* march 2016 - release 7.1

Make sense to you?

Almost: aren't we keeping even numbers for stable (so, 7.2)? But we
have another thread open on that topic.

If you think that these changes should be ported to 7.1.X then probaly
I need a grass71 directory in grass_addons...

Let's avoid that somehow...

Maybe you could modify your modules to detect if user is running 7.0
or 7.1? Martin

Markus