Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, Markus Neteler schrieb am So., 15. Sep. 2019, 16:26: > Hi. > > On Fri, Sep 13, 2019 at 12:26 PM Martin Landa > wrote: > > pá 6. 9. 2019 v 23:40 odesílatel Markus Neteler > napsal: > > > GRASS GIS 7.8.0 with Python 3 support is out: > > > > > > https://github.com/OSGeo/grass/releases/tag/7.8.0 > > > > > > https://trac.osgeo.org/grass/wiki/Release/7.8.0-News > > > > ubuntu packages available from ubuntugis-unstable. Enjoy. Ma > > Also Fedora packages are available now: > > - https://bodhi.fedoraproject.org/updates/FEDORA-2019-bbaea978c7 (testing) > - https://koji.fedoraproject.org/koji/packageinfo?packageID=1972 FYI: It has now reached "stable" state and will be shipped with the upcoming Fedora 31 in October. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi. On Fri, Sep 13, 2019 at 12:26 PM Martin Landa wrote: > pá 6. 9. 2019 v 23:40 odesílatel Markus Neteler napsal: > > GRASS GIS 7.8.0 with Python 3 support is out: > > > > https://github.com/OSGeo/grass/releases/tag/7.8.0 > > > > https://trac.osgeo.org/grass/wiki/Release/7.8.0-News > > ubuntu packages available from ubuntugis-unstable. Enjoy. Ma Also Fedora packages are available now: - https://bodhi.fedoraproject.org/updates/FEDORA-2019-bbaea978c7 (testing) - https://koji.fedoraproject.org/koji/packageinfo?packageID=1972 Markus -- Markus Neteler, PhD https://www.mundialis.de - free data with free software https://grass.osgeo.org https://courses.neteler.org/blog ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, pá 6. 9. 2019 v 23:40 odesílatel Markus Neteler napsal: > GRASS GIS 7.8.0 with Python 3 support is out: > > https://github.com/OSGeo/grass/releases/tag/7.8.0 > > https://trac.osgeo.org/grass/wiki/Release/7.8.0-News ubuntu packages available from ubuntugis-unstable. Enjoy. Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi Martin, Yes, it is indeed not necessarily related. But what about the idea to provide addon-zip-files for download that could be generated in a make routine (make zip, like e.g. here: https://stackoverflow.com/questions/28844155/makefile-generating-zip-files-of-all-sub-folders and then make copy, like e.g. here: https://stackoverflow.com/questions/19509718/how-to-write-a-makefile-to-copy-scripts-to-server)? Cheers Stefan Fra: Martin Landa Sendt: fredag 6. september 2019 21:51:52 Til: Stefan Blumentrath Kopi: Sebastiaan Couwenberg ; grass-dev@lists.osgeo.org Emne: Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support Hi, pá 6. 9. 2019 v 9:24 odesílatel Stefan Blumentrath napsal: > People interested in accessing addon code instantly should be able to deal > with the full addon repo. Maybe splitting up grass7 and grass6 addons in > different repos could reduce the pain a bit? I was thinking to split grass7 and grass6 into different branches. grass7/ -> master/grass7 branch grass6/ -> grass6 branch But it's unrelated to discussed g.extension issue. Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Fri, Sep 6, 2019 at 8:55 PM Markus Neteler wrote: > On Fri, Aug 30, 2019 at 1:51 PM Markus Neteler wrote: > > > > Hi, > > > > Tomorrow, at the FOSS4G 2019 sprint we'll be releasing 7.8.0. > > As we didn't manage..: it shall be tonight. Congratulations to all of you! GRASS GIS 7.8.0 with Python 3 support is out: https://github.com/OSGeo/grass/releases/tag/7.8.0 https://trac.osgeo.org/grass/wiki/Release/7.8.0-News Best, Markus -- Markus Neteler, PhD https://www.mundialis.de - free data with free software https://grass.osgeo.org https://courses.neteler.org/blog ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, pá 6. 9. 2019 v 9:24 odesílatel Stefan Blumentrath napsal: > People interested in accessing addon code instantly should be able to deal > with the full addon repo. Maybe splitting up grass7 and grass6 addons in > different repos could reduce the pain a bit? I was thinking to split grass7 and grass6 into different branches. grass7/ -> master/grass7 branch grass6/ -> grass6 branch But it's unrelated to discussed g.extension issue. Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Fri, Aug 30, 2019 at 1:51 PM Markus Neteler wrote: > > Hi, > > Tomorrow, at the FOSS4G 2019 sprint we'll be releasing 7.8.0. As we didn't manage..: it shall be tonight. Best Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, This does not seem to be trivial, so I do not want to complicate. Personally, I would just be worried that splitting up AddOns in submodules / different repos might lead to incoherence and maintenance issues (esp. updating and improving addons in a community effort). So, from my addon-dev perspective this does not sound very appealing... (As a non-windows user) I read that also the addon situation for Windows is not optimal, but since we do have an auto-build in place could`nt we "just" expand the procedure to provide code of individual addons on a server somewhere (for user convenience). People interested in accessing addon code instantly should be able to deal with the full addon repo. Maybe splitting up grass7 and grass6 addons in different repos could reduce the pain a bit? Cheers Stefan -Original Message- From: grass-dev On Behalf Of Sebastiaan Couwenberg Sent: fredag 6. september 2019 06:53 To: grass-dev@lists.osgeo.org Subject: Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support On 9/6/19 5:18 AM, Vaclav Petras wrote: > On Thu, Sep 5, 2019 at 7:18 AM Martin Landa wrote: >> čt 5. 9. 2019 v 12:48 odesílatel Sebastiaan Couwenberg >> napsal: >>>> that's wrong, g.extension is using 'svn export' (for official repo). >>> >>> Using `svn export` for git repositories makes no sense/is a horrible >> hack. >> >> I agree, so please suggest better solution to avoid that g.extension >> will clone whole repository to install only single addon. Personally >> I have no better idea than to use `svn export`. >> > > Please also note that the latest pre-Git/GitHub g.extension was > primarily not using Subversion, but it was using a nice Trac feature > which allowed to download a zipped subdirectory of the repo, so > Subversion was not a must-have dependency. The idea was to get rid of > build tool dependencies for Python modules as well resulting in no dev > packages needed for Python modules on Linux while possibly getting > arbitrary Python GRASS module code on Windows from Trac or, e.g., from > GitHub which supports downloading of a > (whole) repo (without submodules) as a zip file. `git archive` can create zip or tar.gz files from a repo, with individual addon repos this can replace the Trac feature. If you want to get rid of the build tools on the users system, provide the archive creation as a service on e.g. grass.osgeo.org. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On 9/6/19 5:18 AM, Vaclav Petras wrote: > On Thu, Sep 5, 2019 at 7:18 AM Martin Landa wrote: >> čt 5. 9. 2019 v 12:48 odesílatel Sebastiaan Couwenberg >> napsal: that's wrong, g.extension is using 'svn export' (for official repo). >>> >>> Using `svn export` for git repositories makes no sense/is a horrible >> hack. >> >> I agree, so please suggest better solution to avoid that g.extension >> will clone whole repository to install only single addon. Personally I >> have no better idea than to use `svn export`. >> > > Please also note that the latest pre-Git/GitHub g.extension was primarily > not using Subversion, but it was using a nice Trac feature which allowed to > download a zipped subdirectory of the repo, so Subversion was not a > must-have dependency. The idea was to get rid of build tool dependencies > for Python modules as well resulting in no dev packages needed for Python > modules on Linux while possibly getting arbitrary Python GRASS module code > on Windows from Trac or, e.g., from GitHub which supports downloading of a > (whole) repo (without submodules) as a zip file. `git archive` can create zip or tar.gz files from a repo, with individual addon repos this can replace the Trac feature. If you want to get rid of the build tools on the users system, provide the archive creation as a service on e.g. grass.osgeo.org. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On 9/6/19 5:06 AM, Vaclav Petras wrote: > On Thu, Sep 5, 2019 at 7:50 AM Sebastiaan Couwenberg > wrote: >> >> On 9/5/19 12:54 PM, Markus Neteler wrote: >>> Would shallow clone not clone the entire repo? But we only want a >>> subdirectory out of it. >> >> `git clone --filter` may be an option, or restructure the repo with git >> usage in mind instead of subversion, e.g. using submodules for every >> extension which can then be checked out individually. > > Do you have experience with submodules and some suggested workflow for > updating the code in the submodules? I'm using one submodule in one project > and from my experience, it is extra work comparing to a single repo and it > is quite confusing at times, but I may not be using an optimal workflow. > > What advantages would there be in submodules comparing to addons in > individual repos with some list of modules in a file in another repo, i.e. > something like requirements.txt or PyPI rather than repo subdirectories > which are submodules. I don't use submodules myself, but they would just serve to group the individual repositories into the grass-addons repo. Working on individual addons should be done in the working copy of that specific repo, not the grass-addons one. The idea is mostly to preserve a single point to fetch all for those that want it. For everybody else there are the individual addon repos. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Thu, Sep 5, 2019 at 7:18 AM Martin Landa wrote: > Hi, > > čt 5. 9. 2019 v 12:48 odesílatel Sebastiaan Couwenberg > napsal: > > > that's wrong, g.extension is using 'svn export' (for official repo). > > > > Using `svn export` for git repositories makes no sense/is a horrible > hack. > > I agree, so please suggest better solution to avoid that g.extension > will clone whole repository to install only single addon. Personally I > have no better idea than to use `svn export`. > Please also note that the latest pre-Git/GitHub g.extension was primarily not using Subversion, but it was using a nice Trac feature which allowed to download a zipped subdirectory of the repo, so Subversion was not a must-have dependency. The idea was to get rid of build tool dependencies for Python modules as well resulting in no dev packages needed for Python modules on Linux while possibly getting arbitrary Python GRASS module code on Windows from Trac or, e.g., from GitHub which supports downloading of a (whole) repo (without submodules) as a zip file. ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Thu, Sep 5, 2019 at 7:50 AM Sebastiaan Couwenberg wrote: > > On 9/5/19 12:54 PM, Markus Neteler wrote: > > Would shallow clone not clone the entire repo? But we only want a > > subdirectory out of it. > > `git clone --filter` may be an option, or restructure the repo with git > usage in mind instead of subversion, e.g. using submodules for every > extension which can then be checked out individually. Do you have experience with submodules and some suggested workflow for updating the code in the submodules? I'm using one submodule in one project and from my experience, it is extra work comparing to a single repo and it is quite confusing at times, but I may not be using an optimal workflow. What advantages would there be in submodules comparing to addons in individual repos with some list of modules in a file in another repo, i.e. something like requirements.txt or PyPI rather than repo subdirectories which are submodules. ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On 9/5/19 12:54 PM, Markus Neteler wrote: > Would shallow clone not clone the entire repo? But we only want a > subdirectory out of it. `git clone --filter` may be an option, or restructure the repo with git usage in mind instead of subversion, e.g. using submodules for every extension which can then be checked out individually. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, čt 5. 9. 2019 v 12:48 odesílatel Sebastiaan Couwenberg napsal: > > that's wrong, g.extension is using 'svn export' (for official repo). > > Using `svn export` for git repositories makes no sense/is a horrible hack. I agree, so please suggest better solution to avoid that g.extension will clone whole repository to install only single addon. Personally I have no better idea than to use `svn export`. Thanks, Martin -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Thu, Sep 5, 2019 at 12:48 PM Sebastiaan Couwenberg wrote: > On 9/5/19 12:15 PM, Martin Landa wrote: > > čt 5. 9. 2019 v 11:56 odesílatel Sebastiaan Couwenberg > > napsal: > >> There is still an issue with g.extension using svn export in > >> download_source_code_official_github(): > >> > >> > >> https://github.com/OSGeo/grass/blob/releasebranch_7_8/scripts/g.extension/g.extension.py#L1094 > >> > >> REQUIREMENTS.html also only documents git as a dependency for g.extension: > > > > that's wrong, g.extension is using 'svn export' (for official repo). > > Using `svn export` for git repositories makes no sense/is a horrible hack. > > >> > >> https://github.com/OSGeo/grass/blob/releasebranch_7_8/REQUIREMENTS.html#L210 > >> > >> But g.extension also uses svn in download_source_code_svn(): > >> > >> > >> https://github.com/OSGeo/grass/blob/releasebranch_7_8/scripts/g.extension/g.extension.py#L1066 > > > > download_source_code_svn() is used only when source is 'svn' [1]. > > Let's imagine that user/company has own repository with addons > > maintained by svn. > > Hence the need for REQUIREMENTS.html to list both git & subversion for > g.extension. Yes, to be changed. > > Note that for 'official' source (which is now > > https://github.com/osgeo/grass-addons) [2] is used > > download_source_code_official_github() which is based on 'svn export' > > instead of 'git' [3]. With git the whole repository would need to be > > cloned with full history and all addons modules. That's something we > > would like to avoid. With github 'svn export' trick do the job. Only > > single addons (directory) [which is requested by the user to be > > installed] can be fetched. I hope that we will find better solution in > > the future. > > As mentioned in the thread on the pkg-grass-devel lists [0], use shallow > clone. > > [0] > https://alioth-lists.debian.net/pipermail/pkg-grass-devel/2019-August/079643.html this is unclear to me: Would shallow clone not clone the entire repo? But we only want a subdirectory out of it. Best Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On 9/5/19 12:15 PM, Martin Landa wrote: > čt 5. 9. 2019 v 11:56 odesílatel Sebastiaan Couwenberg > napsal: >> There is still an issue with g.extension using svn export in >> download_source_code_official_github(): >> >> >> https://github.com/OSGeo/grass/blob/releasebranch_7_8/scripts/g.extension/g.extension.py#L1094 >> >> REQUIREMENTS.html also only documents git as a dependency for g.extension: > > that's wrong, g.extension is using 'svn export' (for official repo). Using `svn export` for git repositories makes no sense/is a horrible hack. >> https://github.com/OSGeo/grass/blob/releasebranch_7_8/REQUIREMENTS.html#L210 >> >> But g.extension also uses svn in download_source_code_svn(): >> >> >> https://github.com/OSGeo/grass/blob/releasebranch_7_8/scripts/g.extension/g.extension.py#L1066 > > download_source_code_svn() is used only when source is 'svn' [1]. > Let's imagine that user/company has own repository with addons > maintained by svn. Hence the need for REQUIREMENTS.html to list both git & subversion for g.extension. > Note that for 'official' source (which is now > https://github.com/osgeo/grass-addons) [2] is used > download_source_code_official_github() which is based on 'svn export' > instead of 'git' [3]. With git the whole repository would need to be > cloned with full history and all addons modules. That's something we > would like to avoid. With github 'svn export' trick do the job. Only > single addons (directory) [which is requested by the user to be > installed] can be fetched. I hope that we will find better solution in > the future. As mentioned in the thread on the pkg-grass-devel lists [0], use shallow clone. [0] https://alioth-lists.debian.net/pipermail/pkg-grass-devel/2019-August/079643.html Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, čt 5. 9. 2019 v 11:56 odesílatel Sebastiaan Couwenberg napsal: > There is still an issue with g.extension using svn export in > download_source_code_official_github(): > > > https://github.com/OSGeo/grass/blob/releasebranch_7_8/scripts/g.extension/g.extension.py#L1094 > > REQUIREMENTS.html also only documents git as a dependency for g.extension: that's wrong, g.extension is using 'svn export' (for official repo). > https://github.com/OSGeo/grass/blob/releasebranch_7_8/REQUIREMENTS.html#L210 > > But g.extension also uses svn in download_source_code_svn(): > > > https://github.com/OSGeo/grass/blob/releasebranch_7_8/scripts/g.extension/g.extension.py#L1066 download_source_code_svn() is used only when source is 'svn' [1]. Let's imagine that user/company has own repository with addons maintained by svn. Note that for 'official' source (which is now https://github.com/osgeo/grass-addons) [2] is used download_source_code_official_github() which is based on 'svn export' instead of 'git' [3]. With git the whole repository would need to be cloned with full history and all addons modules. That's something we would like to avoid. With github 'svn export' trick do the job. Only single addons (directory) [which is requested by the user to be installed] can be fetched. I hope that we will find better solution in the future. Ma [1] https://github.com/OSGeo/grass/blob/releasebranch_7_8/scripts/g.extension/g.extension.py#L1230 [2] https://github.com/OSGeo/grass/blob/releasebranch_7_8/scripts/g.extension/g.extension.py#L1228 [3] https://github.com/OSGeo/grass/blob/releasebranch_7_8/scripts/g.extension/g.extension.py#L1115 -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On 9/5/19 10:57 AM, Martin Landa wrote: > út 3. 9. 2019 v 15:47 odesílatel Martin Landa napsal: >> btw, next qgis release is planned for 13.9. [1]. It would be cool to >> release 7.8.0 before this date. > > it's important whether we want RC2 or just go out with final > release... I am expecting next point release 7.8.1 quite soon anyway. There is still an issue with g.extension using svn export in download_source_code_official_github(): https://github.com/OSGeo/grass/blob/releasebranch_7_8/scripts/g.extension/g.extension.py#L1094 REQUIREMENTS.html also only documents git as a dependency for g.extension: https://github.com/OSGeo/grass/blob/releasebranch_7_8/REQUIREMENTS.html#L210 But g.extension also uses svn in download_source_code_svn(): https://github.com/OSGeo/grass/blob/releasebranch_7_8/scripts/g.extension/g.extension.py#L1066 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, út 3. 9. 2019 v 15:47 odesílatel Martin Landa napsal: > btw, next qgis release is planned for 13.9. [1]. It would be cool to > release 7.8.0 before this date. it's important whether we want RC2 or just go out with final release... I am expecting next point release 7.8.1 quite soon anyway. Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, so 31. 8. 2019 v 9:57 odesílatel Martin Landa napsal: btw, next qgis release is planned for 13.9. [1]. It would be cool to release 7.8.0 before this date. Ma [1] https://www.qgis.org/en/site/getinvolved/development/roadmap.html -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, st 14. 8. 2019 v 1:03 odesílatel Markus Neteler napsal: > https://github.com/OSGeo/grass/releases/tag/grass_7_8_0RC1 > > Happy testing and release notes updating, ubuntu package available for testing from Ubuntu Expr PPA [1]. Note only version for bionic (18.04) is available. Unfortunately xenial (16.04) lacks python3-wxgtk4.0 package. It means that xenial will stay will GRASS 7.6 (Python2). Ma [1] https://launchpad.net/~ubuntugis/+archive/ubuntu/ubuntugis-experimental/+packages?field.name_filter=grass_filter=published_filter= -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, Tomorrow, at the FOSS4G 2019 sprint we'll be releasing 7.8.0. Best Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Mon, Aug 5, 2019 at 12:01 PM Markus Neteler wrote: > In addition, pls _all_ help to add content to > * https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures78 ... still a todo. But this page is now way more detailed: > * https://trac.osgeo.org/grass/wiki/Release/7.8.0-News For this I have analysed the ChangeLog since 31 Aug 2018, the date of creation of relbranch76. Still I may have missed something. And finetuning + screenshots might be a good idea as well. > (and we need to find a convenient way to extract that from GitHub). ... anyone? best markusN -- Markus Neteler, PhD https://www.mundialis.de - free data with free software https://grass.osgeo.org https://courses.neteler.org/blog ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Wed, Aug 14, 2019 at 9:04 PM Markus Neteler wrote: > On Wed, Aug 14, 2019 at 8:59 PM Markus Neteler wrote: > > > > On Wed, Aug 14, 2019 at 7:10 PM Sebastiaan Couwenberg > > wrote: > > > On 8/14/19 7:05 PM, Markus Neteler wrote: > > > > It is available now: > > > > https://grass.osgeo.org/grass78/source/grass-7_8_0RC1.tar.gz > > > > https://grass.osgeo.org/grass78/source/grass-7_8_0RC1.md5sum > > > > > > What's with the new naming convention? > > > > > > Can't you replace _ with . in the version? > > > > +1, just realized as well (I try to package for Fedora). > > > > I followed the existing tags but dislike the '_'. > > > > On it... new tarball in some minutes. > > Available now from > https://grass.osgeo.org/grass78/source/ I have also updated the related release to minimize naming confusion: https://github.com/OSGeo/grass/releases Will update the release notes accordingly. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Wed, Aug 14, 2019 at 8:59 PM Markus Neteler wrote: > > On Wed, Aug 14, 2019 at 7:10 PM Sebastiaan Couwenberg > wrote: > > On 8/14/19 7:05 PM, Markus Neteler wrote: > > > It is available now: > > > https://grass.osgeo.org/grass78/source/grass-7_8_0RC1.tar.gz > > > https://grass.osgeo.org/grass78/source/grass-7_8_0RC1.md5sum > > > > What's with the new naming convention? > > > > Can't you replace _ with . in the version? > > +1, just realized as well (I try to package for Fedora). > > I followed the existing tags but dislike the '_'. > > On it... new tarball in some minutes. Available now from https://grass.osgeo.org/grass78/source/ Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Wed, Aug 14, 2019 at 7:10 PM Sebastiaan Couwenberg wrote: > On 8/14/19 7:05 PM, Markus Neteler wrote: > > It is available now: > > https://grass.osgeo.org/grass78/source/grass-7_8_0RC1.tar.gz > > https://grass.osgeo.org/grass78/source/grass-7_8_0RC1.md5sum > > What's with the new naming convention? > > Can't you replace _ with . in the version? +1, just realized as well (I try to package for Fedora). I followed the existing tags but dislike the '_'. On it... new tarball in some minutes. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On 8/14/19 7:05 PM, Markus Neteler wrote: > It is available now: > https://grass.osgeo.org/grass78/source/grass-7_8_0RC1.tar.gz > https://grass.osgeo.org/grass78/source/grass-7_8_0RC1.md5sum What's with the new naming convention? Can't you replace _ with . in the version? -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Wed, Aug 14, 2019 at 3:57 PM Sebastiaan Couwenberg wrote: > On 8/14/19 12:03 AM, Markus Neteler wrote: > > When will the tarballs be available at: > > https://grass.osgeo.org/grass78/source/ It is available now: https://grass.osgeo.org/grass78/source/grass-7_8_0RC1.tar.gz https://grass.osgeo.org/grass78/source/grass-7_8_0RC1.md5sum Best Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On 8/14/19 4:55 PM, Markus Neteler wrote: > On Wed, Aug 14, 2019 at 3:57 PM Sebastiaan Couwenberg wrote: >> On 8/14/19 12:03 AM, Markus Neteler wrote: >> Or should we switch to release tags? > > I don't know what's common for packagers. > Any preferences? tarballs are fine, but not being able to discover new version directories is inconvenient. It requires updating the watch file in the Debian package for every new minor release. The gdal package for example uses download.osgeo.org where everything under /gdal is directory listable (and hence discoverable by uscan(1)). download.osgeo.org is not an option for grasss because it's not being updated, and grass.osgeo.org lacks a directory listing of all grass directories. If pushing new tags is not forgotten, using release tags from the git repository can be better. You just miss artefacts from `make dist`. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Wed, Aug 14, 2019 at 3:57 PM Sebastiaan Couwenberg wrote: > > On 8/14/19 12:03 AM, Markus Neteler wrote: > > it is done! > > Is it? Tagging yes. > > https://github.com/OSGeo/grass/releases/tag/grass_7_8_0RC1 > > When will the tarballs be available at: > > https://grass.osgeo.org/grass78/source/ Later tonight, right now I have no time. Indeed, there might be the glitch that the include/VERSION file was not updated prior to tagging (... not bright enough any more at midnight...). I am still updating the release procedure to the new git(hub) workflow. > Or should we switch to release tags? I don't know what's common for packagers. Any preferences? In any case, the tarball will be uploaded to the usual place on the GRASS server, also in future. With the next (RC) release, it will be all-in-one again but this time the needed updates of the workflow already took many hours, and I ran out of time last night. Best, Markus -- Markus Neteler, PhD https://www.mundialis.de - free data with free software https://grass.osgeo.org https://courses.neteler.org/blog ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On 8/14/19 12:03 AM, Markus Neteler wrote: > it is done! Is it? > https://github.com/OSGeo/grass/releases/tag/grass_7_8_0RC1 When will the tarballs be available at: https://grass.osgeo.org/grass78/source/ Or should we switch to release tags? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, st 14. 8. 2019 v 0:03 odesílatel Markus Neteler napsal: > it is done! > > https://github.com/OSGeo/grass/releases/tag/grass_7_8_0RC1 great. I will try to upload wingrass build and ubuntugis packages ASAP. Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi all, it is done! https://github.com/OSGeo/grass/releases/tag/grass_7_8_0RC1 Happy testing and release notes updating, Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, út 13. 8. 2019 v 0:08 odesílatel Markus Neteler napsal: > > * svn keyword substitution not solved > > Right but we didn't find a solution so far. > > I have polished further svn -> git stuff today, ready for RC1 I'd say. OK. Martin -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Mon, Aug 12, 2019 at 4:47 PM Martin Landa wrote: > ne 11. 8. 2019 v 12:23 odesílatel Markus Neteler napsal: > > I'd say: ready to get RC1 out. > > great, two issues comes to my mind: > > * wingrass builds are currently still down IMHO that does not block RC1. > * svn keyword substitution not solved Right but we didn't find a solution so far. I have polished further svn -> git stuff today, ready for RC1 I'd say. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
El dom., 11 ago. 2019 a las 12:23, Markus Neteler () escribió: > Hi devs, > > On Sun, Aug 4, 2019 at 12:19 PM Markus Neteler wrote: > > What's next: > > > > - GRASS GIS 7.8.0RC1 to be prepared asap > > I have made a series of updates this morning (see commit list on GH). > https://github.com/OSGeo/grass/commits/releasebranch_7_8 > > I'd say: ready to get RC1 out. > +1, it's the best way to get it tested :) Vero ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi devs, On Sun, Aug 4, 2019 at 12:19 PM Markus Neteler wrote: > What's next: > > - GRASS GIS 7.8.0RC1 to be prepared asap I have made a series of updates this morning (see commit list on GH). https://github.com/OSGeo/grass/commits/releasebranch_7_8 I'd say: ready to get RC1 out. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Mon, Aug 5, 2019 at 12:01 PM Markus Neteler wrote: > > On Sun, Aug 4, 2019 at 12:19 PM Markus Neteler wrote: ... > > > - GRASS GIS 7.8.0RC1 to be prepared asap > > I suggest to release it end of this week. ... > Importantly we need to understand if anything is missing for RC1. > Unless we do not publish 7.8 with Python 3 support, we will be soon > removed from various Linux distros as they start to drop Py2-only > versions (i.e. < 7.8). FYI: I have now backported the change of the deprecated shebang #!/usr/bin/env python to #!/usr/bin/env python3 > In addition, pls _all_ help to add content to > * https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures78 > * https://trac.osgeo.org/grass/wiki/Release/7.8.0-News > (and we need to find a convenient way to extract that from GitHub). best markusN ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Mon, Aug 5, 2019 at 10:21 AM Markus Metz wrote: > On Sun, Aug 4, 2019 at 12:19 PM Markus Neteler wrote: ... FYI: I have also updated the CMS with new 7.8 sections. > > What's next: > > > > - GRASS GIS 7.8.0RC1 to be prepared asap I suggest to release it end of this week. > > - fix winGRASS winGRASS mainly depends on Martin and his server. > > - grass77 in master to be changed to grass79 > > +1 done in https://github.com/OSGeo/grass/commit/2f892ffa9bc7d916aa5833c36e704ae1da2e1582 > please let me know if I can help Importantly we need to understand if anything is missing for RC1. Unless we do not publish 7.8 with Python 3 support, we will be soon removed from various Linux distros as they start to drop Py2-only versions (i.e. < 7.8). In addition, pls _all_ help to add content to * https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures78 * https://trac.osgeo.org/grass/wiki/Release/7.8.0-News (and we need to find a convenient way to extract that from GitHub). best markusN ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Sun, Aug 4, 2019 at 12:19 PM Markus Neteler wrote: > > Hi, > > On Sun, Aug 4, 2019 at 10:44 AM Markus Neteler wrote: > > > > > as there were no objections, I have created the new > > > > https://github.com/OSGeo/grass/tree/releasebranch_7_8 > > The needed grass77 -> grass78 updates are covered in: > > https://github.com/OSGeo/grass/pull/74 > (hope I found all needed changes; to go ahead I have merged right away). > > I have also created the cronjobs for weekly tarballs and manual pages: > > https://grass.osgeo.org/grass78/source/snapshot/ > https://grass.osgeo.org/grass78/binary/linux/snapshot/ > https://grass.osgeo.org/grass78/manuals/ > > What's next: > > - GRASS GIS 7.8.0RC1 to be prepared asap > - fix winGRASS > - grass77 in master to be changed to grass79 +1 please let me know if I can help Markus M ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, On Sun, Aug 4, 2019 at 10:44 AM Markus Neteler wrote: > > as there were no objections, I have created the new > > https://github.com/OSGeo/grass/tree/releasebranch_7_8 The needed grass77 -> grass78 updates are covered in: https://github.com/OSGeo/grass/pull/74 (hope I found all needed changes; to go ahead I have merged right away). I have also created the cronjobs for weekly tarballs and manual pages: https://grass.osgeo.org/grass78/source/snapshot/ https://grass.osgeo.org/grass78/binary/linux/snapshot/ https://grass.osgeo.org/grass78/manuals/ What's next: - GRASS GIS 7.8.0RC1 to be prepared asap - fix winGRASS - grass77 in master to be changed to grass79 Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi devs, quite a bit of time has passed, so: On Sun, Jun 23, 2019 at 10:30 PM Markus Neteler wrote: > > Hi, > > time to speed up the GRASS GIS 7.8.0 release! > > On Mon, Apr 1, 2019 at 10:04 AM Martin Landa wrote: > > ne 3. 3. 2019 v 19:33 odesílatel Martin Landa > > napsal: > > > my +1 for creating 7.8 releasebranch. It's a first step which can be > > > done ASAP. Ma > > I believe that it is now overdue to create a new "releasebranch_7_8" > in Github and start to prepare the 7.8.0 release. > > The roadmap is to be defined: > https://trac.osgeo.org/grass/milestone/7.8.0 > > but we need the 7.8.0 release _before_ the FOSS4G conference. > OSGeoLive I don't know as they have the OSGeoLive Feature Freeze on > 25-June-2019. ... this train is already gone. > Anything against the idea of creating the new "releasebranch_7_8" in Github? as there were no objections, I have created the new https://github.com/OSGeo/grass/tree/releasebranch_7_8 GRASS GIS 7.8.0RC1 to be prepared asap. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Markus Neteler wrote > Hi, > > time to speed up the GRASS GIS 7.8.0 release! > > On Mon, Apr 1, 2019 at 10:04 AM Martin Landa > landa.martin@ > wrote: >> ne 3. 3. 2019 v 19:33 odesílatel Martin Landa > landa.martin@ > napsal: >> > my +1 for creating 7.8 releasebranch. It's a first step which can be >> > done ASAP. Ma > > I believe that it is now overdue to create a new "releasebranch_7_8" > in Github and start to prepare the 7.8.0 release. > > The roadmap is to be defined: > https://trac.osgeo.org/grass/milestone/7.8.0 > > but we need the 7.8.0 release _before_ the FOSS4G conference. > OSGeoLive I don't know as they have the OSGeoLive Feature Freeze on > 25-June-2019. > > Anything against the idea of creating the new "releasebranch_7_8" in > Github? +1 as windows is an important user environment, we should look for an joint effort to get back winGRASS dailys. locally winGRASS is compiling here, but not working (see trac ticket)...not sure it's a local issue or more... - best regards Helmut -- Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, ne 23. 6. 2019 v 22:31 odesílatel Markus Neteler napsal: > Anything against the idea of creating the new "releasebranch_7_8" in Github? no objections. Martin -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, time to speed up the GRASS GIS 7.8.0 release! On Mon, Apr 1, 2019 at 10:04 AM Martin Landa wrote: > ne 3. 3. 2019 v 19:33 odesílatel Martin Landa napsal: > > my +1 for creating 7.8 releasebranch. It's a first step which can be > > done ASAP. Ma I believe that it is now overdue to create a new "releasebranch_7_8" in Github and start to prepare the 7.8.0 release. The roadmap is to be defined: https://trac.osgeo.org/grass/milestone/7.8.0 but we need the 7.8.0 release _before_ the FOSS4G conference. OSGeoLive I don't know as they have the OSGeoLive Feature Freeze on 25-June-2019. Anything against the idea of creating the new "releasebranch_7_8" in Github? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hola Martin, El jue., 18 abr. 2019 a las 22:58, Martin Landa () escribió: > Ciao, > > čt 18. 4. 2019 v 22:44 odesílatel Veronica Andreo > napsal: > > It would be nice if the vector digitizer is fixed before release, see > https://trac.osgeo.org/grass/ticket/3777. > > should be fixed in r74401. > partly... see https://trac.osgeo.org/grass/ticket/3777#comment:6 Thanks to you!! (for filling up our inboxes this weekend :D :D) Thanks for your hard work! Cheers, Vero ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Ciao, čt 18. 4. 2019 v 22:44 odesílatel Veronica Andreo napsal: > It would be nice if the vector digitizer is fixed before release, see > https://trac.osgeo.org/grass/ticket/3777. should be fixed in r74401. > I try to do as much testing as I can with python3. Thanks! Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi all, It would be nice if the vector digitizer is fixed before release, see https://trac.osgeo.org/grass/ticket/3777. I try to do as much testing as I can with python3. best, Vero El lun., 8 abr. 2019 a las 14:19, Moritz Lennert (< mlenn...@club.worldonline.be>) escribió: > On 8/04/19 09:35, Martin Landa wrote: > > Hi, > > > > po 1. 4. 2019 v 11:20 odesílatel Moritz Lennert > > napsal: > >> I'm sorry, I have been fairly absent from grass-dev in the last months, > >> and the situation will not get much better in the near future, and so I > >> don't want to block if others are for releasing quickly. Also, I'm not > >> aware of the testing efforts that have already happened (except for > >> Mundialis). Are the automatic tests run systematically in a Python 3 > >> environment ? > > > > no worry, there are very few people testing GRASS in Python3 > > environment. I hope that it will change when there will be RC1 for > > testing available ;-) > > > > To avoid confusion. I am not suggesting to release a buggy version. I > > am just suggesting to start working on release. Creating branch is > > just a first step. Personally I would avoid "technical previews" as we > > did in the past. Just normal release policy as described in RFC. We > > can do more that two RCs if needed. > > Ok, +1 from me for your release plan, but with careful scrutiny before > the actual release. > > Moritz > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On 8/04/19 09:35, Martin Landa wrote: Hi, po 1. 4. 2019 v 11:20 odesílatel Moritz Lennert napsal: I'm sorry, I have been fairly absent from grass-dev in the last months, and the situation will not get much better in the near future, and so I don't want to block if others are for releasing quickly. Also, I'm not aware of the testing efforts that have already happened (except for Mundialis). Are the automatic tests run systematically in a Python 3 environment ? no worry, there are very few people testing GRASS in Python3 environment. I hope that it will change when there will be RC1 for testing available ;-) To avoid confusion. I am not suggesting to release a buggy version. I am just suggesting to start working on release. Creating branch is just a first step. Personally I would avoid "technical previews" as we did in the past. Just normal release policy as described in RFC. We can do more that two RCs if needed. Ok, +1 from me for your release plan, but with careful scrutiny before the actual release. Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, po 1. 4. 2019 v 11:20 odesílatel Moritz Lennert napsal: > I'm sorry, I have been fairly absent from grass-dev in the last months, > and the situation will not get much better in the near future, and so I > don't want to block if others are for releasing quickly. Also, I'm not > aware of the testing efforts that have already happened (except for > Mundialis). Are the automatic tests run systematically in a Python 3 > environment ? no worry, there are very few people testing GRASS in Python3 environment. I hope that it will change when there will be RC1 for testing available ;-) To avoid confusion. I am not suggesting to release a buggy version. I am just suggesting to start working on release. Creating branch is just a first step. Personally I would avoid "technical previews" as we did in the past. Just normal release policy as described in RFC. We can do more that two RCs if needed. Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On 1/04/19 11:09, Martin Landa wrote: Hi, po 1. 4. 2019 v 10:10 odesílatel Moritz Lennert napsal: How good is Python 3 support in trunk currently, especially for wxGui. As would be expected, most errors I've seen in the past seem to be linked either to wxGUI, or to lib/python. Do you think it would be a good idea to create a 7.8 release branch before having solved most of the Python 3 problems, or wouldn't it be better to focus on that in trunk and create the realease branch only once this has reached a reasonable state. I would say that we are not expecting that 7.8.0 will be perfect and all problems/bugs will be solved. If we plan a perfect release that we will never release :-) I obviously agree, but there is a difference between releasing a tech preview or a real release, i.e. something that we officially consider stable (but not perfect). Moreover Python3 support will be widely tested when there will be packages available to install. I would expect that many problems will be discovered after release. Then we can come with a more frequent point releases. So, IIUC, the idea is to create an official release to get more testers ? I'm a bit afraid that if we create an official release and many people hit upon errors that we will actually scare away potential users... But all depends on the actual current usability for a normal user (i.e. someone relying on the GUI). I'm sorry, I have been fairly absent from grass-dev in the last months, and the situation will not get much better in the near future, and so I don't want to block if others are for releasing quickly. Also, I'm not aware of the testing efforts that have already happened (except for Mundialis). Are the automatic tests run systematically in a Python 3 environment ? Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, po 1. 4. 2019 v 10:10 odesílatel Moritz Lennert napsal: > How good is Python 3 support in trunk currently, especially for wxGui. > As would be expected, most errors I've seen in the past seem to be > linked either to wxGUI, or to lib/python. > > Do you think it would be a good idea to create a 7.8 release branch > before having solved most of the Python 3 problems, or wouldn't it be > better to focus on that in trunk and create the realease branch only > once this has reached a reasonable state. I would say that we are not expecting that 7.8.0 will be perfect and all problems/bugs will be solved. If we plan a perfect release that we will never release :-) Moreover Python3 support will be widely tested when there will be packages available to install. I would expect that many problems will be discovered after release. Then we can come with a more frequent point releases. Just my two cents, Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On 1/04/19 10:04, Martin Landa wrote: Hi, ne 3. 3. 2019 v 19:33 odesílatel Martin Landa napsal: my +1 for creating 7.8 releasebranch. It's a first step which can be done ASAP. Ma based on original plan: """ * Proposal of release: 4 Feb 2019 * Soft freeze of release branch: 11 Feb 2019 * RC1: 11 Mar 2019 * RC2: 24 Mar 2019 * RC3: if needed * Final release: 1 Apr 2019 """ an updated plan below :-) """ * Proposal of release: 1 Apr 2019 * Soft freeze of release branch: 8 Apr 2019 * RC1: 6 May 2019 * RC2: 20 May 2019 * RC3: if needed * Final release: 27 May 2019 """ A new branch should be created between April 1 and 8. Make sense to you? How good is Python 3 support in trunk currently, especially for wxGui. As would be expected, most errors I've seen in the past seem to be linked either to wxGUI, or to lib/python. Do you think it would be a good idea to create a 7.8 release branch before having solved most of the Python 3 problems, or wouldn't it be better to focus on that in trunk and create the realease branch only once this has reached a reasonable state. It's a big piece of work and would mean a lot of backporting if there is still a significant amount to do. Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, ne 3. 3. 2019 v 19:33 odesílatel Martin Landa napsal: > my +1 for creating 7.8 releasebranch. It's a first step which can be > done ASAP. Ma based on original plan: """ * Proposal of release: 4 Feb 2019 * Soft freeze of release branch: 11 Feb 2019 * RC1: 11 Mar 2019 * RC2: 24 Mar 2019 * RC3: if needed * Final release: 1 Apr 2019 """ an updated plan below :-) """ * Proposal of release: 1 Apr 2019 * Soft freeze of release branch: 8 Apr 2019 * RC1: 6 May 2019 * RC2: 20 May 2019 * RC3: if needed * Final release: 27 May 2019 """ A new branch should be created between April 1 and 8. Make sense to you? Thanks, Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, ne 3. 3. 2019 v 19:27 odesílatel Markus Neteler napsal: > > - Creation of release branch: 11 Feb 2019 > Please try it out for further testing of GRASS GIS with Python-3! my +1 for creating 7.8 releasebranch. It's a first step which can be done ASAP. Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Mon, Feb 4, 2019 at 5:31 PM Markus Neteler wrote: > > Hi devs, > > currently sitting next to Martin, we updated our roadmap (also keeping > the QGIS releases in mind [1] and the next OSGeoLive release): > > Time schedule: > https://trac.osgeo.org/grass/milestone/7.8.0 > > - Proposal of release: 4 Feb 2019 (OSGeo birthday, btw!) > - Creation of release branch: 11 Feb 2019 > - RC1: 11 Mar 2019 > - RC2: 24 Mar 2019 > - RC3: if needed > - Final release: 1 Apr 2019 (tentatively) Here an update, trying to keep above release plan: We (esp Carmen, Anika and me) are using trunk in a big project in mundialis in which we have completely migrated to Python-3 only. It is all running in the cloud, hence no wxGUI involved. We certainly only use a fraction of all the commands but for sure important ones along with several image processing related addons. Summary: it works :-) In order to ease wider testing, Carmen created a Python-3-only docker image with PDAL included as a goodie (we use it as part of our multi-layered docker images): https://github.com/mundialis/grass-py3-pdal I just added usage instructions there. You can install it in parallel and use it for testing. Please try it out for further testing of GRASS GIS with Python-3! > [1] > https://www.qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule Cheers Markus -- Markus Neteler, PhD https://www.mundialis.de - free data with free software https://grass.osgeo.org https://courses.neteler.org/blog ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
>Time schedule: >https://trac.osgeo.org/grass/milestone/7.8.0 > >- Proposal of release: 4 Feb 2019 (OSGeo birthday, btw!) >- Creation of release branch: 11 Feb 2019 >- RC1: 11 Mar 2019 >- RC2: 24 Mar 2019 >- RC3: if needed >- Final release: 1 Apr 2019 (tentatively) > >For sure an "intensive" plan but we need to move forward. Time to >retire Python-2! >... and if bugs discovered, we can quickly release 7.8.1 etc. looks as an ambitious timeplan, but looks good +1 - best regards Helmut -- Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi devs, currently sitting next to Martin, we updated our roadmap (also keeping the QGIS releases in mind [1] and the next OSGeoLive release): Time schedule: https://trac.osgeo.org/grass/milestone/7.8.0 - Proposal of release: 4 Feb 2019 (OSGeo birthday, btw!) - Creation of release branch: 11 Feb 2019 - RC1: 11 Mar 2019 - RC2: 24 Mar 2019 - RC3: if needed - Final release: 1 Apr 2019 (tentatively) For sure an "intensive" plan but we need to move forward. Time to retire Python-2! ... and if bugs discovered, we can quickly release 7.8.1 etc. [1] https://www.qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule Cheers Markus and Martin ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Thu, Jan 10, 2019 at 7:08 AM Maris Nartiss wrote: > trešd., 2019. g. 9. janv., plkst. 18:47 — lietotājs Markus Neteler > () rakstīja: > > > > On Wed, Jan 9, 2019 at 4:01 PM Maris Nartiss > wrote: > > ... > > > Too late. Python is already broken (I had to fix my scripts; > > > previously working tests are now broken). Do not expect your 7.2/7.4 > > > Python scripts to work with 7.6/7.8 without modifications (depends on > > > functionality in use). > > > > This is weird. Can you elaborate? > Unfortunately I just fixed my code and moved on (as transitioning to > Python 3 has to be done). But here are two examples from the top of my > head: > https://trac.osgeo.org/grass/ticket/3707 > grass.script.parse now returns unicode strings, previously – byte > strings (too lazy to search for a specific revision when it was > introduced). Took a while to understand why calls to an external > library started to fail. > All the recent Python3 changes are in 7.8 only. Pietro did some Python 3 changes early on (not sure which version), unfortunately these were not clearly communicated. In general, all Python API functions should now (since 7.8) return unicode (for both Python 2 and 3), because that's what users would expect with python 3. It's hard to know exactly how much work is still needed, because tests cover just part of the codebase. GUI is mostly working, some issues might come up for less used components, but these are mostly easy to fix, some of the issues are due to the switch to wxPython 4 (wxPython 3 doesn't support Python3). Python components with ctypes need more work. PyGRASS is getting there, tests should be mostly running (not doctests), but there is more work with temporal framework. Add-ons will probably need some small adjustments, but I haven't looked at that. Of course, I am testing only linux now. Anna > > > > Still – it is not so bad – some Python parts never have been working > > > correctly anyway ;-) > > > > Please open ticket(s) if you want to see it fixed. > This is really tricky as for many aspects of GRASS Python code there > are no working examples in the GRASS source or add-ons and thus it is > hard to understand if it is broken or just "I'm holding it the wrong > way" ;-) > I'll try to come up with a test case for raster.history, as it is one > of things I can not get working at the moment. > > > Markus > Māris. > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
trešd., 2019. g. 9. janv., plkst. 18:47 — lietotājs Markus Neteler () rakstīja: > > On Wed, Jan 9, 2019 at 4:01 PM Maris Nartiss wrote: > ... > > Too late. Python is already broken (I had to fix my scripts; > > previously working tests are now broken). Do not expect your 7.2/7.4 > > Python scripts to work with 7.6/7.8 without modifications (depends on > > functionality in use). > > This is weird. Can you elaborate? Unfortunately I just fixed my code and moved on (as transitioning to Python 3 has to be done). But here are two examples from the top of my head: https://trac.osgeo.org/grass/ticket/3707 grass.script.parse now returns unicode strings, previously – byte strings (too lazy to search for a specific revision when it was introduced). Took a while to understand why calls to an external library started to fail. > > Still – it is not so bad – some Python parts never have been working > > correctly anyway ;-) > > Please open ticket(s) if you want to see it fixed. This is really tricky as for many aspects of GRASS Python code there are no working examples in the GRASS source or add-ons and thus it is hard to understand if it is broken or just "I'm holding it the wrong way" ;-) I'll try to come up with a test case for raster.history, as it is one of things I can not get working at the moment. > Markus Māris. ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Wed, Jan 9, 2019 at 4:01 PM Maris Nartiss wrote: ... > Too late. Python is already broken (I had to fix my scripts; > previously working tests are now broken). Do not expect your 7.2/7.4 > Python scripts to work with 7.6/7.8 without modifications (depends on > functionality in use). This is weird. Can you elaborate? > Still – it is not so bad – some Python parts never have been working > correctly anyway ;-) Please open ticket(s) if you want to see it fixed. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Wed, Jan 9, 2019 at 10:01 AM Maris Nartiss wrote: > > trešd., 2019. g. 9. janv., plkst. 14:18 — lietotājs Laurent C. > () rakstīja: > > > > I believe that only a major release could be allowed to break a previously working functionality. It would be very confusing to have a code that work on one version stops working after a minor version bump. > > I my humble opinion it would be contrary to semver that GRASS mostly follows. > Too late. Python is already broken (I had to fix my scripts; > previously working tests are now broken). Do not expect your 7.2/7.4 > Python scripts to work with 7.6/7.8 without modifications (depends on > functionality in use). What was broken? If really some migration is needed, please collect that at some wiki page (I'm not sure which wiki is more suitable here). > > > Still – it is not so bad – some Python parts never have been working > correctly anyway ;-) > > Laurent > Māris. > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
trešd., 2019. g. 9. janv., plkst. 14:18 — lietotājs Laurent C. () rakstīja: > > I believe that only a major release could be allowed to break a previously > working functionality. It would be very confusing to have a code that work on > one version stops working after a minor version bump. > I my humble opinion it would be contrary to semver that GRASS mostly follows. Too late. Python is already broken (I had to fix my scripts; previously working tests are now broken). Do not expect your 7.2/7.4 Python scripts to work with 7.6/7.8 without modifications (depends on functionality in use). Still – it is not so bad – some Python parts never have been working correctly anyway ;-) > Laurent Māris. ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Le mar. 8 janv. 2019 à 00:44, Veronica Andreo a écrit : > El lun., 7 ene. 2019 a las 11:51, Markus Neteler () > escribió: > >> On Mon, Jan 7, 2019 at 11:48 AM Martin Landa >> wrote: >> > po 7. 1. 2019 v 11:41 odesílatel Markus Neteler >> napsal: >> > > - Proposal of release: 7 Jan 2019 >> > > - Creation of release branch: 24 Jan 2019 >> > > - RC1: 1 Feb 2019 >> > > - RC2: 7 Feb 2019 - if needed >> > > - Final release: ~14 Feb 2019 >> > >> > I am afraid that more realistic release date for 7.8 version is >> > ~May/June 2019. Python3 support is not fully done (Anna will know >> > more). > > > I've been mostly testing the temporal modules and many of them fail [0] as > well as many of the temporal tests [1] (dunno if the latter is related to > python3 though). > IMHO, this is one of the parts that might require more work and testing. I > regret I do not know how to answer Anna here: > https://lists.osgeo.org/pipermail/grass-dev/2019-January/090879.html > > >> We don't have Windows builds for testing yet. It also doesn't >> > make sense to me to release 7.6 in January and 7.8 in February. >> >> Personally I would have rather skipped 7.6 but of course that is not >> possible. >> >> > If we >> > want to release Python3-ready GRASS version so early we could >> > integrate it to upcoming version 7.6. >> > > please don't break the temporal framework in 76 > > Vero > > [0] https://trac.osgeo.org/grass/ticket/3727 > [1] https://trac.osgeo.org/grass/ticket/3706 > I believe that only a major release could be allowed to break a previously working functionality. It would be very confusing to have a code that work on one version stops working after a minor version bump. I my humble opinion it would be contrary to semver that GRASS mostly follows. Laurent ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Veronica Andreo wrote >> >> > If we >> > want to release Python3-ready GRASS version so early we could >> > integrate it to upcoming version 7.6. >> > > please don't break the temporal framework in 76 I'm supportive to keep 76 in a productive state Markus Neteler: >> If not, then lets better iron out all issues arising from transition to >> 3. > >Yes, here in mundialis we start to switch. For sure it would be much >easier with a 7.8-release-branch. +1 - best regards Helmut -- Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
El lun., 7 ene. 2019 a las 11:51, Markus Neteler () escribió: > On Mon, Jan 7, 2019 at 11:48 AM Martin Landa > wrote: > > po 7. 1. 2019 v 11:41 odesílatel Markus Neteler > napsal: > > > - Proposal of release: 7 Jan 2019 > > > - Creation of release branch: 24 Jan 2019 > > > - RC1: 1 Feb 2019 > > > - RC2: 7 Feb 2019 - if needed > > > - Final release: ~14 Feb 2019 > > > > I am afraid that more realistic release date for 7.8 version is > > ~May/June 2019. Python3 support is not fully done (Anna will know > > more). I've been mostly testing the temporal modules and many of them fail [0] as well as many of the temporal tests [1] (dunno if the latter is related to python3 though). IMHO, this is one of the parts that might require more work and testing. I regret I do not know how to answer Anna here: https://lists.osgeo.org/pipermail/grass-dev/2019-January/090879.html > We don't have Windows builds for testing yet. It also doesn't > > make sense to me to release 7.6 in January and 7.8 in February. > > Personally I would have rather skipped 7.6 but of course that is not > possible. > > > If we > > want to release Python3-ready GRASS version so early we could > > integrate it to upcoming version 7.6. > please don't break the temporal framework in 76 Vero [0] https://trac.osgeo.org/grass/ticket/3727 [1] https://trac.osgeo.org/grass/ticket/3706 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
>If not, then lets better iron out all issues arising from transition >to 3. winGRASS7.7.svn (standalone and OSGeo4W) already switched to python3, see: https://trac.osgeo.org/grass/ticket/3719 first issues already popped up, see: https://trac.osgeo.org/grass/ticket/3723 more testing welcome. - best regards Helmut -- Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Mon, Jan 7, 2019 at 2:10 PM Maris Nartiss wrote: > pirmd., 2019. g. 7. janv., plkst. 12:51 — lietotājs Markus Neteler > > On Mon, Jan 7, 2019 at 11:48 AM Martin Landa wrote: > > > po 7. 1. 2019 v 11:41 odesílatel Markus Neteler > > > napsal: > > > > - Proposal of release: 7 Jan 2019 > > > > - Creation of release branch: 24 Jan 2019 > > > > - RC1: 1 Feb 2019 > > > > - RC2: 7 Feb 2019 - if needed > > > > - Final release: ~14 Feb 2019 > This really does not seem to be realistic. Agreed - it was meant to be a bit provocative :-) > > > I am afraid that more realistic release date for 7.8 version is > > > ~May/June 2019. Python3 support is not fully done (Anna will know > > > more). We don't have Windows builds for testing yet. It also doesn't > > > make sense to me to release 7.6 in January and 7.8 in February. > > > > Personally I would have rather skipped 7.6 but of course that is not > > possible. > > I fail to see why. Is there any major distro dropping 2.7 support now? Yes, soon, e.g. https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal .. at time scheduled for the next major release, F30. Other distros I was not checking. Essentially it is a matter of relatively short time since Python 2.7 will retire in... (as of now): 0Years 11Months 24Days 3Hours 34Minutes - https://pythonclock.org/ > If not, then lets better iron out all issues arising from transition to 3. Yes, here in mundialis we start to switch. For sure it would be much easier with a 7.8-release-branch. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
pirmd., 2019. g. 7. janv., plkst. 12:51 — lietotājs Markus Neteler () rakstīja: > > On Mon, Jan 7, 2019 at 11:48 AM Martin Landa wrote: > > po 7. 1. 2019 v 11:41 odesílatel Markus Neteler napsal: > > > - Proposal of release: 7 Jan 2019 > > > - Creation of release branch: 24 Jan 2019 > > > - RC1: 1 Feb 2019 > > > - RC2: 7 Feb 2019 - if needed > > > - Final release: ~14 Feb 2019 This really does not seem to be realistic. > > I am afraid that more realistic release date for 7.8 version is > > ~May/June 2019. Python3 support is not fully done (Anna will know > > more). We don't have Windows builds for testing yet. It also doesn't > > make sense to me to release 7.6 in January and 7.8 in February. > > Personally I would have rather skipped 7.6 but of course that is not possible. I fail to see why. Is there any major distro dropping 2.7 support now? If not, then lets better iron out all issues arising from transition to 3. > Markus Māris. ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
On Mon, Jan 7, 2019 at 11:48 AM Martin Landa wrote: > po 7. 1. 2019 v 11:41 odesílatel Markus Neteler napsal: > > - Proposal of release: 7 Jan 2019 > > - Creation of release branch: 24 Jan 2019 > > - RC1: 1 Feb 2019 > > - RC2: 7 Feb 2019 - if needed > > - Final release: ~14 Feb 2019 > > I am afraid that more realistic release date for 7.8 version is > ~May/June 2019. Python3 support is not fully done (Anna will know > more). We don't have Windows builds for testing yet. It also doesn't > make sense to me to release 7.6 in January and 7.8 in February. Personally I would have rather skipped 7.6 but of course that is not possible. > If we > want to release Python3-ready GRASS version so early we could > integrate it to upcoming version 7.6. If that's doable, fine for me. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi, po 7. 1. 2019 v 11:41 odesílatel Markus Neteler napsal: > - Proposal of release: 7 Jan 2019 > - Creation of release branch: 24 Jan 2019 > - RC1: 1 Feb 2019 > - RC2: 7 Feb 2019 - if needed > - Final release: ~14 Feb 2019 I am afraid that more realistic release date for 7.8 version is ~May/June 2019. Python3 support is not fully done (Anna will know more). We don't have Windows builds for testing yet. It also doesn't make sense to me to release 7.6 in January and 7.8 in February. If we want to release Python3-ready GRASS version so early we could integrate it to upcoming version 7.6. Martin -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support
Hi all, the world is eagerly waiting to see the first GRASS GIS 7.8.0 with Python3 support. In my view we need to focus on that and release early. I have drafted a roadmap [1]: - Proposal of release: 7 Jan 2019 - Creation of release branch: 24 Jan 2019 - RC1: 1 Feb 2019 - RC2: 7 Feb 2019 - if needed - Final release: ~14 Feb 2019 This may appear close but we have no other choice than publishing 7.8.0 asap. Essential is the creation of the required release branch. Naturally as much as possible needs to be tested _before_ that, please see https://trac.osgeo.org/grass/wiki/Python3Support#Howtotest Any comments? Markus [1] https://trac.osgeo.org/grass/milestone/7.8.0 -- Markus Neteler, PhD https://www.mundialis.de - free data with free software https://grass.osgeo.org https://courses.neteler.org/blog ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
