Hi All again!

(Sorry about previous half-letter. Just went away without notice. It’s a real 
pain with the online interface for my email provider, and sending from an email 
application will likely be blocked.)


I have now merged configure update to autoconf-2.69 to 7.8 branch [1, 2].

This seems to work fine everywhere, now including Debian unstable too [3], for 
which this autoconf update was an uttermost urgent issue [4].

What remains to be tested is Windows builds. I urge whoever has the possibility 
to test the daily build of 7.8.6dev for Windows to do so.

Best regards,
Nicklas


[1] https://github.com/OSGeo/grass/pull/1867
[2] https://github.com/OSGeo/grass/pull/1870
[3] https://github.com/OSGeo/grass/issues/560
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992810







On Thursday, 16 September 2021, 22:12:39 CEST, Nicklas Larsson 
<n_lars...@yahoo.com> wrote: 







Hi All!


I have now merged configure update [1, 2] to autoconf-2.69 to 7.8 branch

[1]https://github.com/OSGeo/grass/pull/1867
[2]
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992810




On Sunday, 21 March 2021, 09:22:06 CET, Markus Neteler <nete...@osgeo.org> 
wrote: 





Hi devs,

Since the last stable release 7.8.5 almost 70 commits have been accumulated:
https://github.com/OSGeo/grass/compare/7.8.5...releasebranch_7_8

I suggest the following time schedule:

- Soft freeze of release branch: 26 March 2021
- RC1: 6 Apr 2021
- RC2: 16 Apr 2021, if needed
- Final release: 27 Apr 2021

What's still to be done for 7.8.6? See the 7.8.6 milestone, it is
showing the remaining open issues:
https://github.com/OSGeo/grass/milestone/6
--> 78% complete

Please check what really applies to the upcoming 7.8.6 release.

Best,
Markus
_______________________________________________
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

Reply via email to