Re: [GRASS-dev] [release planning] GRASS GIS 8.0.1
Hi, Agreed. It is a small change, affecting only MS Windows and tested successfully. I don`t see any real risk here for breaking anything. https://github.com/OSGeo/grass/pull/2223 is indeed a PR against releasebranch_8_0 that would backport the fix that just needs to get merged. However, if there is any chance to get also https://github.com/OSGeo/grass/pull/2226 (also a tiny change to fix a regression affecting all platforms) merged for 8.0.1, I would really appreciate it. But I understand of course if you rather include that in 8.0.2. Cheers Stefan -Original Message- From: grass-dev On Behalf Of Helmut Kudrnovsky Sent: søndag 20. februar 2022 19:38 To: Grass Dev Subject: [GRASS-dev] [release planning] GRASS GIS 8.0.1 >Hi devs, > >(8.0.1 milestone: >https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOSGeo%2Fgrass%2Fmilestone%2F9data=04%7C01%7CStefan.Blumentrath%40nina.no%7C8382f351aa3f4d56f74e08d9f4a01a4d%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637809791621354784%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=Jy6lWgr8PrCGymRx%2BIXgwAMccSga6JKE%2F0oEFW%2FBRSA%3Dreserved=0) > >I still see backport candidate(s) in >- >https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOSGeo%2Fgrass%2Fissues%3Fq%3Dis%253Aopen%2Bis%253Aissue%2Blabel%253Abackport_needed%2Bmilestone%253A8.0.1data=04%7C01%7CStefan.Blumentrath%40nina.no%7C8382f351aa3f4d56f74e08d9f4a01a4d%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637809791621354784%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=Pa5egZw1F2E1v9WxeCrxSh2U5jPKD482L%2BNxcwGWwM4%3Dreserved=0 > >How to deal with that? regarding: [Bug] winGRASS is missing: libgomp-1.dll, libgfortran-5.dll, libquadmath-0.dll backport_needed some modules don't work cause of missing dependency DLLs. IMHO it is a regression. @ninsbl already prepared a backport PR (https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOSGeo%2Fgrass%2Fpull%2F2223data=04%7C01%7CStefan.Blumentrath%40nina.no%7C8382f351aa3f4d56f74e08d9f4a01a4d%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637809791621354784%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=XtM9S53w7riTeiTqE7RA7OWcnVraFmR%2Bu72VdkCXGnk%3Dreserved=0). so I suggest to backport it. and cut after that directly the release tag? any opinions? kind regards Helmut ___ grass-dev mailing list grass-dev@lists.osgeo.org https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fgrass-devdata=04%7C01%7CStefan.Blumentrath%40nina.no%7C8382f351aa3f4d56f74e08d9f4a01a4d%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637809791621354784%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=1erKtLtfm6fGV4ZAfdZxM44WbmzaUl9qEh3wY94%2F8rA%3Dreserved=0 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 8.0.1
Hi, ne 20. 2. 2022 v 19:37 odesÃlatel Helmut Kudrnovsky napsal: > so I suggest to backport it. and cut after that directly the release tag? any > opinions? +1 for backport. Related to a quick fix for 8.0.0, I will build a new standalone installer 8.0.0-3 and publish soon. 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 8.0.1
>Hi devs, > >(8.0.1 milestone: https://github.com/OSGeo/grass/milestone/9) > >I still see backport candidate(s) in >- >https://github.com/OSGeo/grass/issues?q=is%3Aopen+is%3Aissue+label%3Abackport_needed+milestone%3A8.0.1 > >How to deal with that? regarding: [Bug] winGRASS is missing: libgomp-1.dll, libgfortran-5.dll, libquadmath-0.dll backport_needed some modules don't work cause of missing dependency DLLs. IMHO it is a regression. @ninsbl already prepared a backport PR (https://github.com/OSGeo/grass/pull/2223). so I suggest to backport it. and cut after that directly the release tag? any opinions? kind regards Helmut ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Call for ideas to post in social media
Dear all, Some of you might have seen that every week I post something on Twitter ( https://twitter.com/GRASSGIS - follow us and help with a RT if you don't already ;-)) mainly as a way to show off GRASS new features, releases, student projects, presentations at conferences, scientific publications, new addons, etc. This has brought us +800 more followers in the last year, increased our mentions, impressions and visits significantly (last month our profile visits increased almost 400%). In the long term, I believe increasing our presence and showing our software features is good for the project. To keep this running, we are collecting ideas and crafting threads here: https://trac.osgeo.org/grass/wiki/PSC/Marketing#Upcomingpostsmayberecycledandpostedagain. This upcoming week, I'll post about Caitlin's student grant and the implementation of the temporal class within grass.jupyter. There are a couple of other ideas there that need to be developed further, i.e., they need content. I'm calling here for help with those and for new ideas, screenshots, small video tutorials, new addons, new features you would like to see published in twitter to keep these weekly posts flowing. Thanks much in advance! And thanks to those of you that eventually ping with something cool to show :) Vero ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] RFCs on Python version and release procedure
Dear all, During our last PSC meeting (see minutes here [1]) we discussed the Python language version that we should support and clarifications were made to the draft RFC. Furthermore, the draft RFC for release procedure was also mentioned as a way to adopt feature freezing and avoid last minute backporting of new features that, if not properly tested, might be disruptive (see for example https://github.com/OSGeo/grass/issues/2137). This is a call and invitation to read RFC 4: Release procedure [2] and RFC 8: Python Language Support [3], and comment/discuss on what's drafted there so PSC can then vote and adopt consensuated procedures. Looking forward to hear from you, Vero [1] https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20220211 [2] https://trac.osgeo.org/grass/wiki/RFC/4_ReleaseProcedure [3] https://trac.osgeo.org/grass/wiki/RFC/8_LanguageStandardsSupportPython ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 8.0.1
Hi devs, (8.0.1 milestone: https://github.com/OSGeo/grass/milestone/9) I still see backport candidate(s) in - https://github.com/OSGeo/grass/issues?q=is%3Aopen+is%3Aissue+label%3Abackport_needed+milestone%3A8.0.1 How to deal with that? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
