[GRASS-dev] [release planning] GRASS GIS 7.8.6

neteler · March 21, 2021, 8:21am

Hi devs,

Since the last stable release 7.8.5 almost 70 commits have been accumulated:
https://github.com/OSGeo/grass/compare/7.8.5...releasebranch_7_8

I suggest the following time schedule:

- Soft freeze of release branch: 26 March 2021
- RC1: 6 Apr 2021
- RC2: 16 Apr 2021, if needed
- Final release: 27 Apr 2021

What's still to be done for 7.8.6? See the 7.8.6 milestone, it is
showing the remaining open issues:
https://github.com/OSGeo/grass/milestone/6
--> 78% complete

Please check what really applies to the upcoming 7.8.6 release.

Best,
Markus

neteler · April 7, 2021, 1:05pm

Markus Neteler <neteler@osgeo.org> schrieb am So., 21. März 2021, 09:21:

Hi devs,

Since the last stable release 7.8.5 almost 70 commits have been accumulated:
https://github.com/OSGeo/grass/compare/7.8.5…releasebranch_7_8

I suggest the following time schedule:

Soft freeze of release branch: 26 March 2021

RC1: 6 Apr 2021

RC2: 16 Apr 2021, if needed

Final release: 27 Apr 2021

What’s still to be done for 7.8.6?

Is g.extension failing for all add-ons or only for a few? A new blocker or not?

See the 7.8.6 milestone, it is
showing the remaining open issues:
https://github.com/OSGeo/grass/milestone/6
→ 78% complete

Please check what really applies to the upcoming 7.8.6 release.

Markus

veroandreo · April 12, 2021, 12:47pm

Hi,

Is there anything we can do here before 7.8.6 release: https://lists.osgeo.org/pipermail/grass-dev/2021-April/095084.html

best,

Vero

El mié, 7 abr 2021 a las 15:05, Markus Neteler (<neteler@osgeo.org>) escribió:

Markus Neteler <neteler@osgeo.org> schrieb am So., 21. März 2021, 09:21:

Hi devs,

Since the last stable release 7.8.5 almost 70 commits have been accumulated:
https://github.com/OSGeo/grass/compare/7.8.5…releasebranch_7_8

I suggest the following time schedule:

Soft freeze of release branch: 26 March 2021

RC1: 6 Apr 2021

RC2: 16 Apr 2021, if needed

Final release: 27 Apr 2021

What’s still to be done for 7.8.6?

Is g.extension failing for all add-ons or only for a few? A new blocker or not?

See the 7.8.6 milestone, it is
showing the remaining open issues:
https://github.com/OSGeo/grass/milestone/6
→ 78% complete

Please check what really applies to the upcoming 7.8.6 release.

Markus

grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

neteler · April 12, 2021, 2:15pm

Hi,

Veronica Andreo <veroandreo@gmail.com> schrieb am Mo., 12. Apr. 2021, 14:47:

Hi,

Is there anything we can do here before 7.8.6 release: https://lists.osgeo.org/pipermail/grass-dev/2021-April/095084.html

There is a related discussion in the PROJ list:

https://lists.osgeo.org/pipermail/proj/2021-April/thread.html#10159

Of course we should ship needed fixes (if any) with the upcoming 7.8.6.

Cheers
Markus

best,

Vero

El mié, 7 abr 2021 a las 15:05, Markus Neteler (<neteler@osgeo.org>) escribió:

Markus Neteler <neteler@osgeo.org> schrieb am So., 21. März 2021, 09:21:

Hi devs,

Since the last stable release 7.8.5 almost 70 commits have been accumulated:
https://github.com/OSGeo/grass/compare/7.8.5…releasebranch_7_8

I suggest the following time schedule:

Soft freeze of release branch: 26 March 2021

RC1: 6 Apr 2021

RC2: 16 Apr 2021, if needed

Final release: 27 Apr 2021

What’s still to be done for 7.8.6?

Is g.extension failing for all add-ons or only for a few? A new blocker or not?

See the 7.8.6 milestone, it is
showing the remaining open issues:
https://github.com/OSGeo/grass/milestone/6
→ 78% complete

Please check what really applies to the upcoming 7.8.6 release.

Markus

grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev Mathis

neteler · April 12, 2021, 5:33pm

Hi devs,

On Sun, Mar 21, 2021 at 9:21 AM Markus Neteler <neteler@osgeo.org> wrote:
...

What's still to be done for 7.8.6? See the 7.8.6 milestone, it is
showing the remaining open issues:
https://github.com/OSGeo/grass/milestone/6
--> 78% complete

--> 84% complete

Open questions for anyone with Windows (Helli? Others?):
- Is g.extension failing for all add-ons or only for a few? A new
blocker or not?
- PROJ version in WinGRASS, see
https://lists.osgeo.org/pipermail/grass-dev/2021-April/095084.html

Please check what really applies to the upcoming 7.8.6 release.

I have created a draft release page, pls update as needed:

https://trac.osgeo.org/grass/wiki/Release/7.8.6-News

Best,
Markus

neteler · April 13, 2021, 12:22pm

(moved back into email thread)

On Mon, Apr 12, 2021 at 9:16 PM Helmut Kudrnovsky <hellik@web.de> wrote:

> Markus:
>Open questions for anyone with Windows (Helli? Others?):
>- Is g.extension failing for all add-ons or only for a few? A new
>blocker or not?

winGRASS g.extension is failing for some of the addons where some encoding issues pops up.

but see https://github.com/OSGeo/grass/pull/1496#issuecomment-812447963

>manually set PYTHONUTF8 in C:\OSGeo4W64\apps\grass\grass79\etc\env.bat
>
>[...]
>set PYTHONUTF8=1
>set GRASS_PYTHON=%OSGEO4W_ROOT%\bin\python3.exe
>[...]
>
>then
>
> g.extension extension=i.fusion.hpf
> Downloading precompiled GRASS Addons <i.fusion.hpf>...
> Fetching <i.fusion.hpf> from <http://wingrass.fsv.cvut.cz/grass79/x86_64/addons/grass-7.9.dev/i.fusion.hpf.zip> (be patient)...
> Updating extensions metadata file...
> Updating extension modules metadata file...
> WARNING: No metadata available for module 'constants'.
> WARNING: No metadata available for module 'high_pass_filter'.
> ERROR: Unable to read manual page: [Errno 2] No such file or directory: 'C:\\Users\\youruser\\AppData\\Roaming\\GRASS7\\addons\\docs\\html\\constants.html'

Well, does the file exist?

>at least no fileinput.FileInput error anymore

g.extension works then with these encoding issue addons

this is based upon https://docs.python.org/3/using/windows.html#utf-8-mode

> Windows still uses legacy encodings for the system encoding (the ANSI Code Page). Python uses it for the default encoding of text files (e.g. locale.getpreferredencoding()).
>
> This may cause issues because UTF-8 is widely used on the internet and most Unix systems, including WSL (Windows Subsystem for Linux).
>
> You can use UTF-8 mode to change the default text encoding to UTF-8.

I've tested a bit locally, g.extension works then (beside https://github.com/OSGeo/grass/issues/1499 , though that's a minor issue as all nested addons and helper libs are working, just a nasty warning ); (localized) GUI is mostly working.

though I have no idea if there are any possible side effects with set PYTHONUTF8=1 ....

maybe Anna, Maris have some ideas?

Unfortunately I don't...

should we activate it in master and see what CI test are reporting?

Might be an option to find out.

kind regards
Helmut

ciao,
Markus

annakrat · April 15, 2021, 2:03pm

On Tue, Apr 13, 2021 at 8:22 AM Markus Neteler <neteler@osgeo.org> wrote:

(moved back into email thread)

On Mon, Apr 12, 2021 at 9:16 PM Helmut Kudrnovsky <hellik@web.de> wrote:

Markus:
Open questions for anyone with Windows (Helli? Others?):

Is g.extension failing for all add-ons or only for a few? A new
blocker or not?

winGRASS g.extension is failing for some of the addons where some encoding issues pops up.

but see https://github.com/OSGeo/grass/pull/1496#issuecomment-812447963

manually set PYTHONUTF8 in C:\OSGeo4W64\apps\grass\grass79\etc\env.bat

[…]
set PYTHONUTF8=1
set GRASS_PYTHON=%OSGEO4W_ROOT%\bin\python3.exe
[…]

then

g.extension extension=i.fusion.hpf
Downloading precompiled GRASS Addons <i.fusion.hpf>…
Fetching <i.fusion.hpf> from <http://wingrass.fsv.cvut.cz/grass79/x86_64/addons/grass-7.9.dev/i.fusion.hpf.zip> (be patient)…
Updating extensions metadata file…
Updating extension modules metadata file…
WARNING: No metadata available for module ‘constants’.
WARNING: No metadata available for module ‘high_pass_filter’.
ERROR: Unable to read manual page: [Errno 2] No such file or directory: ‘C:\Users\youruser\AppData\Roaming\GRASS7\addons\docs\html\constants.html’

Well, does the file exist?

at least no fileinput.FileInput error anymore

g.extension works then with these encoding issue addons

this is based upon https://docs.python.org/3/using/windows.html#utf-8-mode

Windows still uses legacy encodings for the system encoding (the ANSI Code Page). Python uses it for the default encoding of text files (e.g. locale.getpreferredencoding()).

This may cause issues because UTF-8 is widely used on the internet and most Unix systems, including WSL (Windows Subsystem for Linux).

You can use UTF-8 mode to change the default text encoding to UTF-8.

I’ve tested a bit locally, g.extension works then (beside https://github.com/OSGeo/grass/issues/1499 , though that’s a minor issue as all nested addons and helper libs are working, just a nasty warning ); (localized) GUI is mostly working.

though I have no idea if there are any possible side effects with set PYTHONUTF8=1 …

maybe Anna, Maris have some ideas?

Honestly this discussion is hard to follow, I would have to dive more in… I think PYTHONUTF8=1 is fine, there may be a few issues, but probably worth it.

Unfortunately I don’t…

should we activate it in master and see what CI test are reporting?

Might be an option to find out.

kind regards
Helmut

ciao,
Markus

grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

neteler · May 5, 2021, 9:03pm

Hi devs,

On Mon, Apr 12, 2021 at 7:33 PM Markus Neteler <neteler@osgeo.org> wrote:

On Sun, Mar 21, 2021 at 9:21 AM Markus Neteler <neteler@osgeo.org> wrote:
...
> What's still to be done for 7.8.6? See the 7.8.6 milestone, it is
> showing the remaining open issues:
> https://github.com/OSGeo/grass/milestone/6
> --> 78% complete

--> 84% complete

--> 100% as I have bumped the remaining six open PRs to the new milestone 7.8.7.

Open questions for anyone with Windows (Helli? Others?):
- Is g.extension failing for all add-ons or only for a few? A new
blocker or not?

We are stuck here. But I do not want to postpone the release forever.

- PROJ version in WinGRASS, see
https://lists.osgeo.org/pipermail/grass-dev/2021-April/095084.html

No idea either.

> Please check what really applies to the upcoming 7.8.6 release.

I have created a draft release page, pls update as needed:

https://trac.osgeo.org/grass/wiki/Release/7.8.6-News

Updated again
(changes: https://trac.osgeo.org/grass/wiki/Release/7.8.6-News?action=diff&version=3&old_version=1)

I suggest that we release RC1 asap.

Best,
Markus

--
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog

mlennert · May 6, 2021, 6:09am

Am 5. Mai 2021 23:03:04 MESZ schrieb Markus Neteler <neteler@osgeo.org>:

Hi devs,

On Mon, Apr 12, 2021 at 7:33 PM Markus Neteler <neteler@osgeo.org> wrote:

On Sun, Mar 21, 2021 at 9:21 AM Markus Neteler <neteler@osgeo.org> wrote:
...
> What's still to be done for 7.8.6? See the 7.8.6 milestone, it is
> showing the remaining open issues:
> https://github.com/OSGeo/grass/milestone/6
> --> 78% complete

--> 84% complete

--> 100% as I have bumped the remaining six open PRs to the new milestone 7.8.7.

Open questions for anyone with Windows (Helli? Others?):
- Is g.extension failing for all add-ons or only for a few? A new
blocker or not?

We are stuck here. But I do not want to postpone the release forever.

I don't want to block the release, but in my experience g.extension not working correctly is something that leads to a very frustrating user experience on Windows, so would be great if this could be solved before.

Moritz

Blumentrath_Stefan1 · May 6, 2021, 8:29am

Hi,

I did a quick check with GRASS 7.8.5: https://gist.github.com/ninsbl/8051f51d372b565ca6f5a29b480d2463
~ 25 AddOn modules are affected for various reasons.
Most common issues are lack of manual pages...

For some it may be fixed on the addon site, but for modules with libraries, g.extention might have to be fixed (did not look at the details yet).

Cheers
Stefan

-----Original Message-----
From: grass-dev <grass-dev-bounces@lists.osgeo.org> On Behalf Of Moritz Lennert
Sent: torsdag 6. mai 2021 08:10
To: grass-dev@lists.osgeo.org; Markus Neteler <neteler@osgeo.org>; GRASS developers list <grass-dev@lists.osgeo.org>
Subject: Re: [GRASS-dev] [release planning] GRASS GIS 7.8.6

Am 5. Mai 2021 23:03:04 MESZ schrieb Markus Neteler <neteler@osgeo.org>:

Hi devs,

On Mon, Apr 12, 2021 at 7:33 PM Markus Neteler <neteler@osgeo.org> wrote:

On Sun, Mar 21, 2021 at 9:21 AM Markus Neteler <neteler@osgeo.org> wrote:
...
> What's still to be done for 7.8.6? See the 7.8.6 milestone, it is
> showing the remaining open issues:
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
> ithub.com%2FOSGeo%2Fgrass%2Fmilestone%2F6&data=04%7C01%7C%7C335
> d0aa4554c4afef30608d910558cf7%7C6cef373021314901831055b3abf02c73%7C
> 0%7C0%7C637558781906330143%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAw
> MDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata
> =zwJNFpzyVz5beaiy297ECcgzFBmaNRgU%2B7rENlhDWyU%3D&reserved=0
> --> 78% complete

--> 84% complete

--> 100% as I have bumped the remaining six open PRs to the new milestone 7.8.7.

Open questions for anyone with Windows (Helli? Others?):
- Is g.extension failing for all add-ons or only for a few? A new
blocker or not?

We are stuck here. But I do not want to postpone the release forever.

I don't want to block the release, but in my experience g.extension not working correctly is something that leads to a very frustrating user experience on Windows, so would be great if this could be solved before.

Moritz
_______________________________________________
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-dev&data=04|01||335d0aa4554c4afef30608d910558cf7|6cef373021314901831055b3abf02c73|0|0|637558781906340135|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=eiiNrrJ47kkJwKG%2BkQDNs1s9V0yfr9%2BFb5uT4pAWHIc%3D&reserved=0

mlennert · May 6, 2021, 9:43am

On 6/05/21 10:29, Stefan Blumentrath wrote:

Hi,

I did a quick check with GRASS 7.8.5: https://gist.github.com/ninsbl/8051f51d372b565ca6f5a29b480d2463
~ 25 AddOn modules are affected for various reasons.
Most common issues are lack of manual pages...

For some it may be fixed on the addon site, but for modules with libraries, g.extention might have to be fixed (did not look at the details yet).

Problems that are caused by the addons themselves should obviously not be considered blockers of a release, so we should focus on the issues directly caused by g.extension.

IIUC, they all are caused because the addon is either a toolset with several modules, or there are library files in the directory or in subdirectories (e.g. i.segment.hierarchical and r.estimap.recreation). The relevant zip file does contain all necessary files for running the addon, so it is g.extension that is looking for info that it shouldn't look for.

Moritz

-----Original Message-----
From: grass-dev <grass-dev-bounces@lists.osgeo.org> On Behalf Of Moritz Lennert
Sent: torsdag 6. mai 2021 08:10
To: grass-dev@lists.osgeo.org; Markus Neteler <neteler@osgeo.org>; GRASS developers list <grass-dev@lists.osgeo.org>
Subject: Re: [GRASS-dev] [release planning] GRASS GIS 7.8.6

Am 5. Mai 2021 23:03:04 MESZ schrieb Markus Neteler <neteler@osgeo.org>:

Hi devs,

On Mon, Apr 12, 2021 at 7:33 PM Markus Neteler <neteler@osgeo.org> wrote:

On Sun, Mar 21, 2021 at 9:21 AM Markus Neteler <neteler@osgeo.org> wrote:
...

What's still to be done for 7.8.6? See the 7.8.6 milestone, it is
showing the remaining open issues:
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
ithub.com%2FOSGeo%2Fgrass%2Fmilestone%2F6&data=04%7C01%7C%7C335
d0aa4554c4afef30608d910558cf7%7C6cef373021314901831055b3abf02c73%7C
0%7C0%7C637558781906330143%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAw
MDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata
=zwJNFpzyVz5beaiy297ECcgzFBmaNRgU%2B7rENlhDWyU%3D&reserved=0
--> 78% complete

--> 84% complete

--> 100% as I have bumped the remaining six open PRs to the new milestone 7.8.7.

Open questions for anyone with Windows (Helli? Others?):
- Is g.extension failing for all add-ons or only for a few? A new
blocker or not?

We are stuck here. But I do not want to postpone the release forever.

I don't want to block the release, but in my experience g.extension not working correctly is something that leads to a very frustrating user experience on Windows, so would be great if this could be solved before.

Moritz
_______________________________________________
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-dev&data=04|01||335d0aa4554c4afef30608d910558cf7|6cef373021314901831055b3abf02c73|0|0|637558781906340135|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=eiiNrrJ47kkJwKG%2BkQDNs1s9V0yfr9%2BFb5uT4pAWHIc%3D&reserved=0

Blumentrath_Stefan1 · May 6, 2021, 1:57pm

OK, here is a PR to address this issue on Windows:
https://github.com/OSGeo/grass/pull/1565

-----Original Message-----
From: Moritz Lennert <mlennert@club.worldonline.be>
Sent: torsdag 6. mai 2021 11:43
To: Stefan Blumentrath <Stefan.Blumentrath@nina.no>; grass-dev@lists.osgeo.org; Markus Neteler <neteler@osgeo.org>
Subject: Re: [GRASS-dev] [release planning] GRASS GIS 7.8.6

On 6/05/21 10:29, Stefan Blumentrath wrote:

Hi,

I did a quick check with GRASS 7.8.5:
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist
.github.com%2Fninsbl%2F8051f51d372b565ca6f5a29b480d2463&data=04%7C
01%7C%7C36a7365f2ac2443bc0b008d910735784%7C6cef373021314901831055b3abf
02c73%7C0%7C0%7C637558909848248089%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4
wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sda
ta=uNLOhYw2P5f5DPzTM54ldGO%2BSZdKvp6Ai6MZ4Kz1WZI%3D&reserved=0
~ 25 AddOn modules are affected for various reasons.
Most common issues are lack of manual pages...

For some it may be fixed on the addon site, but for modules with libraries, g.extention might have to be fixed (did not look at the details yet).

Problems that are caused by the addons themselves should obviously not be considered blockers of a release, so we should focus on the issues directly caused by g.extension.

IIUC, they all are caused because the addon is either a toolset with several modules, or there are library files in the directory or in subdirectories (e.g. i.segment.hierarchical and r.estimap.recreation).
The relevant zip file does contain all necessary files for running the addon, so it is g.extension that is looking for info that it shouldn't look for.

Moritz

-----Original Message-----
From: grass-dev <grass-dev-bounces@lists.osgeo.org> On Behalf Of
Moritz Lennert
Sent: torsdag 6. mai 2021 08:10
To: grass-dev@lists.osgeo.org; Markus Neteler <neteler@osgeo.org>;
GRASS developers list <grass-dev@lists.osgeo.org>
Subject: Re: [GRASS-dev] [release planning] GRASS GIS 7.8.6

Am 5. Mai 2021 23:03:04 MESZ schrieb Markus Neteler <neteler@osgeo.org>:

Hi devs,

On Mon, Apr 12, 2021 at 7:33 PM Markus Neteler <neteler@osgeo.org> wrote:

On Sun, Mar 21, 2021 at 9:21 AM Markus Neteler <neteler@osgeo.org> wrote:
...

What's still to be done for 7.8.6? See the 7.8.6 milestone, it is
showing the remaining open issues:
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
ithub.com%2FOSGeo%2Fgrass%2Fmilestone%2F6&data=04%7C01%7C%7C335
d0aa4554c4afef30608d910558cf7%7C6cef373021314901831055b3abf02c73%7C
0%7C0%7C637558781906330143%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAw
MDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata
=zwJNFpzyVz5beaiy297ECcgzFBmaNRgU%2B7rENlhDWyU%3D&reserved=0
--> 78% complete

--> 84% complete

--> 100% as I have bumped the remaining six open PRs to the new milestone 7.8.7.

Open questions for anyone with Windows (Helli? Others?):
- Is g.extension failing for all add-ons or only for a few? A new
blocker or not?

We are stuck here. But I do not want to postpone the release forever.

I don't want to block the release, but in my experience g.extension not working correctly is something that leads to a very frustrating user experience on Windows, so would be great if this could be solved before.

Moritz
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist
s.osgeo.org%2Fmailman%2Flistinfo%2Fgrass-dev&data=04%7C01%7C%7C36a
7365f2ac2443bc0b008d910735784%7C6cef373021314901831055b3abf02c73%7C0%7
C0%7C637558909848248089%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLC
JQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3kOm%2Fj
IJ8k2uzuH2h%2FNt%2Bp%2BZn4OyVBhMGEZnRUKANqs%3D&reserved=0

neteler · May 18, 2021, 7:49am

On Thu, May 6, 2021 at 11:43 AM Moritz Lennert
<mlennert@club.worldonline.be> wrote:

On 6/05/21 10:29, Stefan Blumentrath wrote:
> Hi,
>
> I did a quick check with GRASS 7.8.5: https://gist.github.com/ninsbl/8051f51d372b565ca6f5a29b480d2463
> ~ 25 AddOn modules are affected for various reasons.
> Most common issues are lack of manual pages...
>
> For some it may be fixed on the addon site, but for modules with libraries, g.extention might have to be fixed (did not look at the details yet).

Problems that are caused by the addons themselves should obviously not
be considered blockers of a release, so we should focus on the issues
directly caused by g.extension.

With the recent PR merges and backports I assume that the addon
installation problem has be addressed (thanks to all involved!).

May we go towards 7.8.6 RC1 at this point?

Markus

nila · May 18, 2021, 7:22pm

I think we should wait for an agreement of the PR [1] addressing the GDAL 3.3 conflict with GRASS [2], which will become a trivial yet serious issue when GDAL 3.3 becomes more widely distributed.

Best,
Nicklas

[1] https://github.com/OSGeo/grass/pull/1567
[2] https://github.com/OSGeo/grass/issues/1563

On Tuesday, 18 May 2021, 09:49:31 CEST, Markus Neteler neteler@osgeo.org wrote:

On Thu, May 6, 2021 at 11:43 AM Moritz Lennert
<mlennert@club.worldonline.be> wrote:

On 6/05/21 10:29, Stefan Blumentrath wrote:

Hi,

I did a quick check with GRASS 7.8.5: https://gist.github.com/ninsbl/8051f51d372b565ca6f5a29b480d2463
~ 25 AddOn modules are affected for various reasons.
Most common issues are lack of manual pages…

For some it may be fixed on the addon site, but for modules with libraries, g.extention might have to be fixed (did not look at the details yet).

Problems that are caused by the addons themselves should obviously not
be considered blockers of a release, so we should focus on the issues
directly caused by g.extension.

With the recent PR merges and backports I assume that the addon
installation problem has be addressed (thanks to all involved!).

May we go towards 7.8.6 RC1 at this point?

Markus

grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

nila · May 19, 2021, 9:56am

The GDAL 3.3 conflict has been resolved. Thanks Markus M!
I have no further objections to proceed with 7.8.6 RC1.

Cheers,
Nicklas

On Tuesday, 18 May 2021, 21:22:22 CEST, Nicklas Larsson via grass-dev grass-dev@lists.osgeo.org wrote:

I think we should wait for an agreement of the PR [1] addressing the GDAL 3.3 conflict with GRASS [2], which will become a trivial yet serious issue when GDAL 3.3 becomes more widely distributed.

Best,
Nicklas

[1] https://github.com/OSGeo/grass/pull/1567
[2] https://github.com/OSGeo/grass/issues/1563

On Tuesday, 18 May 2021, 09:49:31 CEST, Markus Neteler neteler@osgeo.org wrote:

On Thu, May 6, 2021 at 11:43 AM Moritz Lennert
<mlennert@club.worldonline.be> wrote:

On 6/05/21 10:29, Stefan Blumentrath wrote:

Hi,

I did a quick check with GRASS 7.8.5: https://gist.github.com/ninsbl/8051f51d372b565ca6f5a29b480d2463
~ 25 AddOn modules are affected for various reasons.
Most common issues are lack of manual pages…

For some it may be fixed on the addon site, but for modules with libraries, g.extention might have to be fixed (did not look at the details yet).

Problems that are caused by the addons themselves should obviously not
be considered blockers of a release, so we should focus on the issues
directly caused by g.extension.

With the recent PR merges and backports I assume that the addon
installation problem has be addressed (thanks to all involved!).

May we go towards 7.8.6 RC1 at this point?

Markus

grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

neteler · May 19, 2021, 6:18pm

On Wed, May 19, 2021 at 11:56 AM Nicklas Larsson <n_larsson@yahoo.com> wrote:

The GDAL 3.3 conflict has been resolved. Thanks Markus M!
I have no further objections to proceed with 7.8.6 RC1.

Excellent!

I have updated this document:
https://trac.osgeo.org/grass/wiki/Release/7.8.6-News

Ready for RC1, I'd say!

Markus

neteler · June 10, 2021, 4:37pm

Hi devs,

GRASS GIS 7.8.6RC1 has been released 22 days ago,
https://github.com/OSGeo/grass/releases/tag/7.8.6RC1

and no major issues happened. One fix (plus translations update) has
been applied since then:

https://github.com/OSGeo/grass/commit/83c45339c98e7b587aa218a5731226ac8f6cb355

Do we need another RC for this or release anyway?

Markus

--
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog

veroandreo · June 10, 2021, 6:50pm

What about this one https://github.com/OSGeo/grass/issues/1594? Shall we bump it to 7.8.7 and move forward? I vote, yes

El jue, 10 jun 2021 a las 18:38, Markus Neteler (<neteler@osgeo.org>) escribió:

Hi devs,

GRASS GIS 7.8.6RC1 has been released 22 days ago,
https://github.com/OSGeo/grass/releases/tag/7.8.6RC1

and no major issues happened. One fix (plus translations update) has
been applied since then:

https://github.com/OSGeo/grass/commit/83c45339c98e7b587aa218a5731226ac8f6cb355

Do we need another RC for this or release anyway?

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

neteler · June 23, 2021, 11:57am

El jue, 10 jun 2021 a las 18:38, Markus Neteler (<neteler@osgeo.org>) escribió:

Hi devs,

GRASS GIS 7.8.6RC1 has been released 22 days ago,
https://github.com/OSGeo/grass/releases/tag/7.8.6RC1

and no major issues happened. One fix (plus translations update) has
been applied since then:

https://github.com/OSGeo/grass/commit/83c45339c98e7b587aa218a5731226ac8f6cb355

Do we need another RC for this or release anyway?

The 7.8.6 milestone: 100% complete
https://github.com/OSGeo/grass/milestone/6

On Thu, Jun 10, 2021 at 8:50 PM Veronica Andreo <veroandreo@gmail.com> wrote:

What about this one https://github.com/OSGeo/grass/issues/1594? Shall we bump it to 7.8.7 and move forward? I vote, yes

Ok, bumped to 7.8.7.

I have updated again this document:
https://trac.osgeo.org/grass/wiki/Release/7.8.6-News

Important question: with the planned Addon repo structure affect
g.extension of G7?

Markus

wenzeslaus · June 24, 2021, 2:45am

On Wed, Jun 23, 2021 at 7:58 AM Markus Neteler <neteler@osgeo.org> wrote:

Important question: with the planned Addon repo structure affect
g.extension of G7?

If we want to make backports from v8 to v7 addons easier, then we need to create another branch for v7 (besides the one for v8) and restructure v7 as we did v6 and will restructure the v8 branch.

The master branch would stay as a read-only legacy in this scenario. The alternative is leaving the master branch for v7.

https://github.com/OSGeo/grass-addons/issues/528