[Geoserver-users] GeoServer 2.20-RC Release Candidate available for testing

The GeoServer 2.20-RC Release Candidate is available for testing, see release announcement for a tour of what is new, improved and fixed!

Thanks to Jody for working on the release and fixing the website download pages.

GeoServer is produced by a whole team of contributors and committers … and also you as a part of the GeoServer Community. Helping test a release candidate is your chance to contribute directly providing testing and feedback on new functionality and double checking if your favourite bug is fixed.

We ask everyone (individuals, organizations, service providers) to:

  1. Download the release candidate
  2. Test with your own data
  3. Reply to this email (even just to say hi)

Participating in testing release candidates is a key expectation of our open source social contract. We make an effort to thank each person who tests in our release announcement and project presentations!

A reminder that GeoServer commercial service providers are fully expected to test on behalf of their customers.

···


GeoServer Project Steering Committee
Open Source Geospatial Foundation

A small bit of testing from me - apparently the release note links are no longer public (and require you to login?)

https://osgeo-org.atlassian.net/secure/ReleaseNote.jspa?projectId=10000&version=16815

  • I can see that link as part of the jira project team.
  • When trying to sign in by one of the OAuth approaches (googe, apple, etc…) it complains if I do not share my email address and wants to send offers from Atlassian (sigh)

Reporting issue here https://osgeo-org.atlassian.net/browse/GEOS-10237

···


Jody Garnett

Hi Jody, all,

Thanks to the community for helping maintain GeoServer.

I tested a data directory migration from 2.17.1 to 2.20-RC on Windows using Tomcat.

SQL Server, Control flow, and Importer extensions all looking good.

Once this version is released I think probably time we upgraded.

Cheers.

image001.png

image334c27.PNG

image003.jpg

···

Russell Grew | Data Manager
Douglas Partners Pty Ltd | ABN 75 053 980 117 | www.douglaspartners.com.au
96 Hermitage Road West Ryde NSW 2114 | PO Box 472 West Ryde NSW 1685

Facebook

LinkedIn

To find information on our COVID-19 measures, please visit douglaspartners.com.au/news/covid-19


If you are not the intended recipient of this email, please notify us immediately and be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited.

From: Jody Garnett <jody.garnett@…84…>
Sent: Thursday, 16 September 2021 9:02 AM
To: GeoServer Users geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] GeoServer 2.20-RC Release Candidate available for testing

The GeoServer 2.20-RC Release Candidate is available for testing, see release announcement for a tour of what is new, improved and fixed!

Thanks to Jody for working on the release and fixing the website download pages.

GeoServer is produced by a whole team of contributors and committers … and also you as a part of the GeoServer Community. Helping test a release candidate is your chance to contribute directly providing testing and feedback on new functionality and double checking if your favourite bug is fixed.

We ask everyone (individuals, organizations, service providers) to:

  1. Download the release candidate

  2. Test with your own data

  3. Reply to this email (even just to say hi)

Participating in testing release candidates is a key expectation of our open source social contract. We make an effort to thank each person who tests in our release announcement and project presentations!

A reminder that GeoServer commercial service providers are fully expected to test on behalf of their customers.

GeoServer Project Steering Committee

Open Source Geospatial Foundation

Wanted to report back one other oddness, if you are using geoserver dependencies downstream in a war overlay, the vector tile extension is providing a conflicting version of JTS via a transitive dependency.

The result is two jts jars (and geoserver unwilling to function), not sure if there is anything that can be done here.

To fix add an exclude when depending on gs-vectortiles:

org.geoserver.extension gs-vectortiles org.locationtech.jts jts-core
···


Jody Garnett