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:
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!
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)
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
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:
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!
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: