we rather urgently need to publish trunk as the new stable version in
order to get rid of the current Python2 issues.
Python2 is close to EOL and being slowly dropped. Our interfaces to
other software including QGIS require Python3. Also packaging becomes
increasingly difficult on various operating systems as well as the
usage of GRASS GIS in cloud environments (Openshift etc).
I would suggest to only publish a single release of GRASS GIS 7.6 and
to concentrate on the 7.8 release with Python3 support.
Hence, I propose to start a new releasebranch_7_8 asap.
Again, we need to come to speed with Python3 support in terms of
actually releasing it and the current trunk version looks works quite
well.
We may discuss to make 7.6 LTS and 7.4 EOL but many distros won't
allow to update to 7.6 nor a 7.6 LTS will motivate us to avoid
backporting and focus on 7.8
Am 27. Dezember 2018 10:38:39 MEZ schrieb Markus Neteler <neteler@osgeo.org>:
Dear all,
we rather urgently need to publish trunk as the new stable version in
order to get rid of the current Python2 issues.
Python2 is close to EOL and being slowly dropped. Our interfaces to
other software including QGIS require Python3. Also packaging becomes
increasingly difficult on various operating systems as well as the
usage of GRASS GIS in cloud environments (Openshift etc).
I would suggest to only publish a single release of GRASS GIS 7.6 and
to concentrate on the 7.8 release with Python3 support.
Hence, I propose to start a new releasebranch_7_8 asap.
Again, we need to come to speed with Python3 support in terms of
actually releasing it and the current trunk version looks works quite
well.
We may discuss to make 7.6 LTS and 7.4 EOL but many distros won't
allow to update to 7.6 nor a 7.6 LTS will motivate us to avoid
backporting and focus on 7.8
we rather urgently need to publish trunk as the new stable version in
order to get rid of the current Python2 issues.
Python2 is close to EOL and being slowly dropped. Our interfaces to
other software including QGIS require Python3. Also packaging becomes
increasingly difficult on various operating systems as well as the
usage of GRASS GIS in cloud environments (Openshift etc).
I would suggest to only publish a single release of GRASS GIS 7.6 and
to concentrate on the 7.8 release with Python3 support.
Hence, I propose to start a new releasebranch_7_8 asap.
Again, we need to come to speed with Python3 support in terms of
actually releasing it and the current trunk version looks works quite
well.
We may discuss to make 7.6 LTS and 7.4 EOL but many distros won't
allow to update to 7.6 nor a 7.6 LTS will motivate us to avoid
backporting and focus on 7.8
Il giorno gio 27 dic 2018, 10:38 Markus Neteler <neteler@osgeo.org> ha scritto:
Dear all,
Dears,
We may discuss to make 7.6 LTS and 7.4 EOL but many distros won’t
allow to update to 7.6 nor a 7.6 LTS will motivate us to avoid
backporting and focus on 7.8
Opinions?
Are we sure that a so big change does not require a major release, moving forward to 8.0?
I remember already some discussion about it but I don’t remember if we arrive to a conclusion.
On Thu, Dec 27, 2018 at 12:18 PM Luca Delucchi <lucadeluge@gmail.com> wrote:
Il giorno gio 27 dic 2018, 10:38 Markus Neteler <neteler@osgeo.org> ha scritto:
...
Are we sure that a so big change does not require a major release, moving forward to 8.0?
I remember already some discussion about it but I don't remember if we arrive to a conclusion.
AFAIK there was no conclusion.
Keep in mind that changing to grass80 will break most of the existing
interfaces (QGIS, R, ...) which rely on grass7x for startup. It will
take a long time for them to catch up and propagate their needed
changes through their update channels.
And Python3 support is rather a "must" nowadays, rather a big bugfix
than a new feature.
My suggestion would be to see it in a rather pragmatic way and use V8
to roll out e.g. a new raster format.
I agree that we need tp release GRASS with python 3 support as soon as possible and 7.8 seems more feasible
than 8.0. I would like to hear from Anna on how much much is needed and whether she or Vashek need to spend
some significant time on it (which would be OK with me as this is a critical need). They are on vacation at this time
so I am not sure whether they will respond (Martin may have talked to them recently).
Helena
On Dec 27, 2018, at 6:26 AM, Markus Neteler <neteler@osgeo.org> wrote:
On Thu, Dec 27, 2018 at 12:18 PM Luca Delucchi <lucadeluge@gmail.com> wrote:
Il giorno gio 27 dic 2018, 10:38 Markus Neteler <neteler@osgeo.org> ha scritto:
...
Are we sure that a so big change does not require a major release, moving forward to 8.0?
I remember already some discussion about it but I don't remember if we arrive to a conclusion.
AFAIK there was no conclusion.
Keep in mind that changing to grass80 will break most of the existing
interfaces (QGIS, R, ...) which rely on grass7x for startup. It will
take a long time for them to catch up and propagate their needed
changes through their update channels.
And Python3 support is rather a "must" nowadays, rather a big bugfix
than a new feature.
My suggestion would be to see it in a rather pragmatic way and use V8
to roll out e.g. a new raster format.
Helena Mitasova
Professor at the Department of Marine,
Earth, and Atmospheric Sciences
Associate director and faculty fellow at the Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
hmitaso@ncsu.edu http://geospatial.ncsu.edu/osgeorel/publications.html
"All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.”
