Most of these don't affect the Mac and there are more pressing issues for 
coloring vectors than the #3196 and #3206 IMHO (e.g., see #3126-3128). So OK 
with me to release 8.3.1 to fix a couple of really major issues and bump the 
others to 8.3.2.

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 Oct 22, 2023, at 12:00 PM, grass-dev-requ...@lists.osgeo.org wrote:

Date: Sun, 22 Oct 2023 14:27:57 +0200
From: Markus Neteler <nete...@osgeo.org<mailto:nete...@osgeo.org>>
To: GRASS developers list 
<grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>>
Subject: Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1
Message-ID:
<CALFmHhtv5areiqHhRvkaXg=8k86deogijw5cphvywekeuhm...@mail.gmail.com<mailto:CALFmHhtv5areiqHhRvkaXg=8k86deogijw5cphvywekeuhm...@mail.gmail.com>>
Content-Type: text/plain; charset="UTF-8"

Hi devs,

Still 6 items to go or bump to the 8.3.2 milestone:
https://urldefense.com/v3/__https://github.com/OSGeo/grass/issues?q=is*3Aopen*label*3A*22backport*to*8.3*22*milestone*3A8.3.1__;JSslJSsrJSsl!!IKRxdwAv5BmarQ!ZZlVQcxd8ELL0evmQ9tvYVnHAgAIg7IoynvKPdv_C1dGVz7uyh27k26_rVs7VTUeFS-LTB6FNssO3RQceRO23rxbMXIFrKCRl20$

Given the urgency of 8.3.1 final I suggest to merge what's possible
and bump the rest.
Or, rather bump all and release 8.3.1 final.

Markus

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

Reply via email to