GeoServer 3.0-RC freeze & feedback

Good day folks,

Wow the new UI / UX is looknig great! With that in mind it is time to make a release candidate … this Friday. I will ask for a code freeze Thursday (while we will not new main branches on build server we will be adjusting how releases are tagged for GeoServer).

  • ImageN
  • ImageIO
  • GeoTools
  • GeoWebCache
  • mapfish-print-v2
  • GeoServer

The release candidate is focused on the core application and extensions.

Congrats everyone - the release candidate is now available:

The planned change to 3.0.0-SNAPSHOT did not proceed due to difficulties passing cite and acceptance tests. These two jobs use Makefile to assemble a war quickly, however the use of -DskipTests does not work cleanly when starting a new version sequence. The test classification dependences are not considered when establishing build order, forcing the build to depend on osgeo report to have these artifacts from a prior run.

I am in the process of preparing a fix using -Dmaven.test.skip=true that uses a profile to exclude test classification dependencies and have it working for:

  • cite
  • acceptance
  • allExtensions

This is a tricky issue to catch as we can only see it when making a new version.

Hi Jody,

Thanks for the marvelous update.

I miss the Geoserver jar’s with version 3.0-RC in repo.osgeo.org. Is that due to the work with new tag, or do I look in the wrong repo?

Best regards,

Roar Brænden

It may be an issue with the deploy, let’s check the builder server.

https://repo.osgeo.org/repository/geoserver-snapshots/org/geoserver/community/gs-proxy-base-ext/3.0-SNAPSHOT/maven-metadata.xml

:-1: It looks like the build server did not change to the correct branch and was uploading 3.0-SNAPSHOT, will this is why we issue a release candidate to learn about these problems.

:+1: I can confirm that the tag GitHub - geoserver/geoserver at 3.0-RC · GitHub has the correct version. If I get an opportunity this week I will deploy to osgeo from the tag … but for today your feedback is successful in that we learned of a glitch.

Update: Now fixed!

Possible Oracle issue raised GeoServer 3 Oracle OCI TNS problem by @dcal

Keycloak feedback: Allow Keycloak composite roles to access workspaces and layers - #6 by birke-kb

Deprecated core → extensions: 3.0-RC: ImageMosaic Fails On Missing Class

FileBlobStore 3.0-RC: Feedback Cannot Create Blob

osgeo release Nexus repo GeoServer 3.0-RC Release Candidate - #2 by aorzech

Hi Roar,

I’ve just deployed the 3.0-RC jars manually on the repo

Cheers
Andrea

Thanks, now I got to see the new version.

And it is really great!

Best regards,

Roar Brænden

1 Like

Regression due to new UI: NODE_OPTS not working

Docs: Make cluster nodes identifiable from the GUI - GeoServer Documentation