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

2023-09-20 Thread Nicklas Larsson via grass-dev
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  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  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  on behalf of Markus 
>> Neteler 
>> Sent: Monday, September 11, 2023 6:26 AM
>> To: GRASS developers list 
>> 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


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

2023-09-11 Thread Michael Barton
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<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<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-requ...@lists.osgeo.org wrote:

Date: Mon, 11 Sep 2023 12:26:03 +0200
From: Markus Neteler mailto:nete...@osgeo.org>>
To: GRASS developers list 
mailto:grass-dev@lists.osgeo.org>>
Subject: [GRASS-dev] [release planning] GRASS GIS 8.3.1
Message-ID:
mailto:calfmhhux1ihkwfiuby4upsjtrfwgafszdc4jt9bdo7uwork...@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

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


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

2023-09-11 Thread Markus Neteler
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
https://lists.osgeo.org/mailman/listinfo/grass-dev