GeoServer/GeoTools PMC Meeting at 18:30 CET / 9:30 PDT tomorrow

jive · April 21, 2026, 5:40pm

GeoTools / GeoServer PMC meeting - 2026-04-21

jody: Contact OGC about CITE for 3.0.0
* Asked can just certify 3.0.0 and replace 2.28 sticker on website
(no response yet)

Release is out:

GeoServer 3.0-RC Release
Failed to transition to 3.0.0-SNAPSHOT ahead of release, so this is a 3.0-RC rather than 3.0.0-RC as planned (see next topic)
Blog post has a nice intro to the new context-driven user experience
Windows installer not available, as CERT expired, Juan working with OSGeo to replace it (it is more annoying this year).

Planning:

There should be a blog post about the crowdfunding milestone 3? Perhaps for the 3.0.0 release …

Discussion about CERT:

Can we get a warning? Email? Schedule issue in the future?
Idea: We could add a reminder to the release schedule wiki page … it is where we do future planning.
- note: When we get new cert, and understand when it expires, update the release schedule page

Feedback thread on discourse:

The release did not deploy 3.0-RC to osgeo nexus
- jody: checkout 3.0-RC tag and deploy manually
Question about keycloak, answer is in discourse
- Good content for update instructions
Question: Blobstore failure, Jody could not reproduce
Question: Oracle: Reply to Daniel

The UX and theme looks great!

To look forward to:

Updating translations, and identifying which keys not used
- Transflix vs Weblate → Weblate
  https://docs.geoserver.org/latest/en/developer/translation/#translating-the-ui
  (thanks Alexandre Gacon!)

Sidebar: about pending heading:

https://github.com/geoserver/geoserver/wiki/GSIP-233
oseo - broken right now
oidc - asked to be an extension, no response about pending yet
- ask on discourse thread - done
notice some extensions are not included yet:
- page lists 59 items, downloads have 55…
  - 3 GeoFence plugins not ready yet, listed in the release page with broken links (Client, Postgres Backend, WPS)
  - Importer BDB Backend is also listed, but has been removed for several releases - release page should be updated.

mkdocs is live! Congrats

discussion about adopting theme elements from the UI for docs:

We could go dark, rather than blue, for dark mode
- option: Drop box to just the SVG logo mark, rather than have the word GeoServer show up in blue on blue?
- option: Have dark mode go black (or dark gray) and light mode go page color, then the blue GeoServer always shows up

For offline docs we need to link to internal directory/idex.md always.

The website will generate directory/ references for website, and directory/index.html for offline use.
The page.md references are fine

Fun links:

Q: Can we take the theme to the geoserver.org website
A: That would be amazing what would we do

take the top menubar and gradient from? Yes
It is hard to give up our full logo (with word GeoServer)
- options: Make the SVG accept colour input ..
  - Torben: Will try and give that a try
  - Kevin gave this a try previously and ran into browser security features
- Actually if the dark mode takes the top area dark then we are fine, and light mode has the top being white, then the blue “GeoServer” always shows up

Tip: Use snippets to inline content:

    **Linux**

    --8<--  
    doc/en/user/installation/jdk-linux-guidance.txt
    --8<--

Discussion about headings on upgrade instructions:

Make a heading “Upgrading GeoServer 3.0.0 Guidance” and remove from subheadings?

Discussion about interface - some feedback around improved context:

With a layer group selected, view Layers doesn’t show that these are the layers belonging to the layer group in the page description
When editing a single layer while in a workspace, modifying the layer returns you to the layer page without the workspace context selected

Jody had trouble with the RC process and release script:

GSIP-226 proposes changing to 3.0.0-SNAPSHOT, and then 3.0.1-SNAPSHOT
- And having the tags visible in commit history
- Last moment decision to go with merge commit, rather than code freeze
Glitch: When building from a new version, not everything works with -DskipTests
- Does not take the test classifiers into account when making module builder order plan
  - Affects the CITE and acceptance workflows
  - wcs10 and wcs11 extensions are not part of build, but build uses them for testing, specifically the test jar for testing

Gabe has a workaround, do several builds module by modules

Jody tried two approaches:

profile with -DskipTests activation, andrea asked to use mven.test.skip=true
here is the PR:
https://github.com/geoserver/geoserver/pull/9418
- hard to review as it affects the entire codebase
- cite and acceptance work, but final assembly is missing app-schema-tests
  (not sure quite how to handle that)