https://github.com/OSGeo/grass/issues/3077 <https://github.com/OSGeo/grass/issues/3077> _is_ the one and only blocker for 8.3.1. :
https://github.com/OSGeo/grass/issues?q=is%3Aopen+is%3Aissue+label%3A%22backport+to+8.3%22+label%3Ablocker <https://github.com/OSGeo/grass/issues?q=is:open+is:issue+label:%22backport+to+8.3%22+label:blocker> N. > On 20 Sep 2023, at 17:14, Newcomb, Doug <doug_newc...@fws.gov> wrote: > > I wouldn't mind seeing the fix to g.extension for Windows that just went in, > so you can load addons on Windows in 8.3.x > https://github.com/OSGeo/grass/pull/3166#issuecomment-1727462938 > <https://github.com/OSGeo/grass/pull/3166#issuecomment-1727462938> > <https://github.com/OSGeo/grass/pull/3166#issuecomment-1727462938> > g.extension: fix installing addons on the OS MS Windows by tmszi · Pull > Request #3166 · OSGeo/grass > <https://github.com/OSGeo/grass/pull/3166#issuecomment-1727462938> > Fixes #3077. Fix installing addons via g.extension module on the OS MS > Windows without dependency on Git program. Gettings official GitHub addons > repository branches g.extension -l is based on the ... > github.com <http://github.com/> > > From: grass-dev <grass-dev-boun...@lists.osgeo.org > <mailto:grass-dev-boun...@lists.osgeo.org>> on behalf of Nicklas Larsson via > grass-dev <grass-dev@lists.osgeo.org <mailto:grass-dev@lists.osgeo.org>> > Sent: Wednesday, September 20, 2023 4:14 AM > To: Markus Neteler <nete...@osgeo.org <mailto:nete...@osgeo.org>> > Cc: GRASS developers list <grass-dev@lists.osgeo.org > <mailto:grass-dev@lists.osgeo.org>> > Subject: [EXTERNAL] Re: [GRASS-dev] [release planning] GRASS GIS 8.3.1 > > > This email has been received from outside of DOI - Use caution before > clicking on links, opening attachments, or responding. > > > In general, I wouldn’t mind a quick patch 8.3.1 release. Remaining > (non-blocking) issues may be bumped to 8.3.2, which in turn can be released > as soon as possible. > > The changes since 8.3.0: > https://github.com/OSGeo/grass/compare/8.3.0...OSGeo:grass:releasebranch_8_3?expand=1 > > <https://github.com/OSGeo/grass/compare/8.3.0...OSGeo:grass:releasebranch_8_3?expand=1> > > > Best, > Nicklas > > >> On 19 Sep 2023, at 21:33, Markus Neteler <nete...@osgeo.org >> <mailto:nete...@osgeo.org>> wrote: >> >> Any other opinions? >> What about the Windows g.extension git story, to be added to 8.3.1? >> >> Markus >> >> On Mon, Sep 11, 2023 at 1:48 PM Newcomb, Doug <doug_newc...@fws.gov >> <mailto:doug_newc...@fws.gov>> wrote: >>> >>> This is an important function of GRASS. I think it would be wise to rectify >>> the issue as soon as possible >>> >>> ________________________________ >>> From: grass-dev <grass-dev-boun...@lists.osgeo.org >>> <mailto:grass-dev-boun...@lists.osgeo.org>> on behalf of Markus Neteler >>> <nete...@osgeo.org <mailto:nete...@osgeo.org>> >>> Sent: Monday, September 11, 2023 6:26 AM >>> To: GRASS developers list <grass-dev@lists.osgeo.org >>> <mailto:grass-dev@lists.osgeo.org>> >>> Subject: [EXTERNAL] [GRASS-dev] [release planning] GRASS GIS 8.3.1 >>> >>> Hi devs, >>> >>> While 8.3.0 has been released rather recently, an important bug showed up: >>> - r.watershed: fix streams and basins #3140 >>> >>> Unfortunately r.watershed is partially broken in 8.3.0 such that >>> streams and basins are no longer correctly calculated. This has been >>> now been fixed. >>> >>> Given the importance of r.watershed, I suggest an anticipated release of >>> 8.3.1 >>> >>> Here the milestone: >>> https://github.com/OSGeo/grass/milestone/21 >>> <https://github.com/OSGeo/grass/milestone/21> >>> >>> What do you think? >>> >>> Markus >>> _______________________________________________ >>> grass-dev mailing list >>> grass-dev@lists.osgeo.org >> _______________________________________________ >> grass-dev mailing list >> grass-dev@lists.osgeo.org <mailto: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