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> 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> 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> on behalf of Markus >> Neteler <nete...@osgeo.org> >> Sent: Monday, September 11, 2023 6:26 AM >> To: GRASS developers list <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 >> >> What do you think? >> >> Markus >> _______________________________________________ >> grass-dev mailing list >> grass-dev@lists.osgeo.org > _______________________________________________ > 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
