GeoServer PSC meeting notes, May 5th 2026

GeoServer GeoServer Developer
,
1

GeoTools / GeoServer PMC meeting - 2026-05-05

Attending

  • Torben Barsballe

  • Cécile Vuilleumier

  • Peter Smythe

  • Gabriel Roldan

  • Jukka Rahkonen

  • Kevin Smith

  • Andrea Aime

  • Pierre Mauduit

  • Jody Garnett

Actions from prior meetings:

  • non selezionata|17.599999999999998pxx17.599999999999998px

    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)

  • non selezionata|17.599999999999998pxx17.599999999999998px

    jody: checkout 3.0-RC tag and deploy manually

Agenda

  1. Certificate to sign Windows builds

  2. CITE tests for GeoServer 3.x

  3. Preview links in 3.x

  4. Longer runway for 2.28.x

  5. Chit chat

Actions

  • non selezionata|17.599999999999998pxx17.599999999999998px

Certificate to sign Windows builds

The certificate is already there.

The group that provides the certificate no longer sends to projects, but instead the maintainer needs to log into their system and obtain it; the process has gotten more difficult, but is currently in progress.

CITE tests for GeoServer 3.x

Waiting for funding, looking into it.
OGC certifies a very specific version, any change requires a new certification (changing plugins or even data can affect the certification).

Preview links in 3.x

https://github.com/geoserver/geoserver/pull/9457

Tension:

  • List of links allow for copying

  • But list of links can grow uncontrollably

  • Names are not well separated (rounded rectangles around the names would address this)

Peter: would be nice to have a dropdown-like experience, but with the ability to copy the links.

Gabriel: there might be a way to tell a max length of an element in CSS and have the browser automatically add the … and handle expansion. To be looked at.

Jukka: links might end up taking more real estate than the capabilities links

Also, check if there are aliases and eliminate the duplicates (CSV).

Longer runway for 2.28.x

Geosolutions proposal, one extra year of runway for GeoServer, with releases once every 4 months. What’s needed is to just retain the build machinery on the build server,

Counter: it would disincentivize upgrades to 3.x.

GeoServer home page wise, 2.28.x will disappear anyways from the home page links once 3.1.0 is out (but be available from the archives).