[GRASS-dev] Release policy: towards an urgent GRASS GIS release with Python3 support

[Helena Mitasova]

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 at osgeo.org> wrote:
> 
> On Thu, Dec 27, 2018 at 12:18 PM Luca Delucchi <lucadeluge at gmail.com> wrote:
>> Il giorno gio 27 dic 2018, 10:38 Markus Neteler <neteler at 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.
> 
> my2cents,
> Markus
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev

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 at 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.”