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

[Vaclav Petras]

The grass7 branch is created. See #571 for the changes in the structure.

I think releasing now without the changes and then releasing again soon
with the extension changes is an okay solution.

https://github.com/OSGeo/grass-addons/pull/571

On Thu, Jun 24, 2021 at 4:12 AM Stefan Blumentrath <
Stefan.Blumentrath at nina.no> wrote:

> Hi,
>
>
>
> As for the changes in g.extension, I think they are necessary as e.g. here:
>
>
> https://github.com/OSGeo/grass/blob/70e0c0ef9c7ce4e971c5197a4010ce5eaf354433/scripts/g.extension/g.extension.py#L1615
>
> “grass7” is hardcoded in the URL.
>
>
>
> A solution would be to first check if the "source_url" with "grass7"
>
> (https://github.com/OSGeo/grass-addons/tree/master/grass7/) exists and
> otherwise assign the new URL without "grass7".
>
>
>
> As Vasek points out, first a decision has to be made about the final URL
> (or branch) in
>
> https://github.com/OSGeo/grass-addons/issues/528
>
>
>
> Here:
>
> https://github.com/OSGeo/grass/pull/1678
>
> is a draft PR for a possible approach to this. It may have to be
> backported to 7.6 or even 7.4?
>
> g.extension in G7.8 already supports branches, so if there will be a
> branch for different versions, that should be easy to adjust in g.extension.
>
>
>
> We should probably wait a bit with restructuring the addon repo until a
> modified version of g.extension has been packaged for the most essential
> OS/distros at least…
>
> See: https://repology.org/project/grass/versions
>
>
>
> g.extension in G8 can then be streamlined to the new repo structure…
>
>
>
> Cheers
>
> Stefan
>
>
>
>
>
> *From:* grass-dev <grass-dev-bounces at lists.osgeo.org> *On Behalf Of *Vaclav
> Petras
> *Sent:* torsdag 24. juni 2021 04:45
> *To:* Markus Neteler <neteler at osgeo.org>
> *Cc:* GRASS developers list <grass-dev at lists.osgeo.org>
> *Subject:* Re: [GRASS-dev] [release planning] GRASS GIS 7.8.6
>
>
>
>
>
>
>
> On Wed, Jun 23, 2021 at 7:58 AM Markus Neteler <neteler at 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
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOSGeo%2Fgrass-addons%2Fissues%2F528&data=04%7C01%7C%7C2f4d86cd092a4fe22fff08d936ba2c82%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637600995508223342%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=0T7F1SOqEuIDE3Hd7z9p5gKVZrF%2FT9iF8mTzYeMOaH0%3D&reserved=0>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20210627/03122f11/attachment.html>