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

I wondered why I was getting such weird results while trying to create a demo for class. I agree that a new release is needed. IIRC, I also reported a bug that made the cartographic composer unusable. I think that is now fixed too?

MIchael


C. Michael Barton
Associate Director, School of Complex Adaptive Systems (https://scas.asu.edu)
Professor, School of Human Evolution & Social Change (https://shesc.asu.edu)
Director, Center for Social Dynamics & Complexity (https://complexity.asu.edu)
Arizona State University
Tempe, AZ 85287-2701
USA

Executive Director, Open Modeling Foundation (https://openmodelingfoundation.github.io)
Director, Network for Computational Modeling in Social & Ecological Sciences (https://comses.net)

personal website: http://www.public.asu.edu/~cmbarton

On Sep 11, 2023, at 12:00 PM, grass-dev-request@lists.osgeo.org wrote:

Date: Mon, 11 Sep 2023 12:26:03 +0200
From: Markus Neteler <neteler@osgeo.org>
To: GRASS developers list <grass-dev@lists.osgeo.org>
Subject: [GRASS-dev] [release planning] GRASS GIS 8.3.1
Message-ID:
<CALFmHhux1iHkwFiubY4upSjtRfwgaFsZdc4jt9bdO7uWorKFog@mail.gmail.com>
Content-Type: text/plain; charset=“UTF-8”

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://urldefense.com/v3/https://github.com/OSGeo/grass/milestone/21;!!IKRxdwAv5BmarQ!fLYx2qXSePiDD7YriDiwhfhRuNHC5933BaxX2ZHhtXlzqP5G7IwXHxmQ-htvX8cxngFn5fMA9BONPmY5f5eTwwt8OIoJ4fXIryY$

What do you think?

Markus