GeoServer PSC meeting notes, Feb 25th 2025

aaime-geosolutions · February 25, 2025, 6:27pm

GeoTools / GeoServer PMC meeting - 2025-02-25

Attending

Torben Barsballe
Jukka Rahkonen
Peter Smythe
Kevin Smith
Gabriel Roldan
Andrea Aime
Jody Garnett

Actions from prior meetings:

[image]Gabe: Send for 2.27.x-cloud, 2.26.x-cloud integration branches to discourse

I’ll wait a couple weeks until sanitizing the branches in gscloud to have clean patches to contribute upstream

[image]All: Help requested handling CVE Disclosure updates, volunteer on geoserver-security!

Agenda

CITE tests updates
Build Server Cert - Expiry Notifications Ending
Maven 3.9 as minimum version
Endgame for GeoServer 2.27.0

Actions

[image]Jody: Motion to direct prior funds generated for CITE certification to direct towards Andrea, Peter, Gabe, and those who contributed as appropriate.
[image]Peter: Add notes to developers guide on how to make this repeatable
[image]Andrea: Clean up CITE build server jobs that are not in use please (done)

CITE tests updates

Help requested from OSGeo: #10 - GeoServer CITE certification - standards-committee - OSGeo Git Services: Gitea - Git with a cup of tea

WMTS 1.0 fixes:

github.com/geoserver/geoserver

Run CITE WMTS 1.0 tests

geoserver:main ← aaime:cite_wmts

opened 06:22PM - 04 Jan 25 UTC

aaime

+744 -43

This one quickly became epic, and required changes: * In GWC, see https://githu…b.com/GeoWebCache/geowebcache/pull/1342 (depends onto it) * In the test suite, see https://github.com/geoserver/ets-wmts10/tree/schema_invalid_i_j * In GeoServer (this PR). In addition, not all tests are being run due to https://github.com/opengeospatial/ets-wmts10/issues/47 I need to figure out how to get those going, but in the meantime, it's good to have 45 tests passing (covers caps and tile fetching, only in KVP mode). # Checklist - [x] I have read the [contribution guidelines](https://github.com/geoserver/geoserver/blob/main/CONTRIBUTING.md). - [x] I have sent a [Contribution Licence Agreement](https://docs.geoserver.org/latest/en/developer/policies/committing.html) (not required for small changes, e.g., fixing typos in documentation). - [x] First PR targets the `main` branch (backports managed later; ignore for branch specific issues). - [ ] All the build checks are green ([see automated QA checks](https://docs.geoserver.org/latest/en/developer/qa-guide/index.html)). For core and extension modules: - [ ] New unit tests have been added covering the changes. - [ ] [Documentation](https://github.com/geoserver/geoserver/tree/main/doc/en/user/source) has been updated (if change is visible to end users). - [ ] The [REST API docs](https://github.com/geoserver/geoserver/tree/main/doc/en/api/1.0.0) have been updated (when changing configuration objects or the REST controllers). - [ ] There is an issue in the [GeoServer Jira](https://osgeo-org.atlassian.net/browse/GEOS/summary) (except for changes that do not affect administrators or end users in any way). - [ ] Commit message(s) must be in the form ``[GEOS-XYZWV] Title of the Jira ticket``. - [ ] Bug fixes and small new features are presented as a single commit. - [ ] Each commit has a single objective (if there are multiple commits, each has a separate JIRA ticket describing its goal).

Need to get two fixes merged before we can get it work with production TE:

Peter:

Discussing 2.27.0 certification, we can get the certification on the pre-announced artifacts so that announcement can also be about certification.

Todo:

Follow up with OGC members (Simone,Jeroen,Angelos) so that the above PRs are prioritized for cite OGC work
GeoPackage testing possible
GeoTIFF testing possible

Discussion:

What else can be considered? CSW, KML, GML, …
WPS 1.0 was fine, WPS 2.0 implementation (EMF Bindings, etc…)
- Rather implement OGC API - Process
WCS 2.0 stuck

Action:

Jody: Prior funds were generated for CITE certification, make a motion to direct towards Andrea, Peter, Gabe, and those who contributed as appropriate.
Peter: Add notes to developers guide on how to make this repeatable
Andrea: Clean up CITE build server jobs that are not in use please [done]

Build Server Cert - Expiry Notifications Ending

Let’s encrypt notifications, just before we were going to test the discourse group thing.

Suggestions:

monitoring service - Red Sift
Do we need monitoring? Failed once in 4 years
Consider asking OSGeo to “add us to their list” or something … Jody will chat with OSGeo about red sift (which is free up to 250 certs).

Discourse feedback:

Seven day autoclose on topics? GeoServer builds should not autoclose …Done.

Maven 3.9 as minimum version

See email, maven 3.9 is needed to address maven plugin warnings.

No difference in default plugin versions for 3.8 or 3.9 … so can we do 3.8 minimum.

Gabe to change the pull request to use 3.8

Endgame for GeoServer 2.27.0

What do we expect? 3 weeks to go…

CITE passing anticipated:

Ticket for each test, so Peter can have fun closing!
Peter is updating developers’ guides with how a release manager can get certification for a release.
- Do we want to certify each release?
  - major version: 2.27.0, 2.28.0, …
  - minor releases: 2.27.1 not without automation too much heavy on release maker
For major release we should consider a separate helper for certification, as release manager is already doing version / build workcal

Things we would like, but have no budget:

Some improvements for OGC API - Features docs, things like CQL2
- CQL2 docs are better this time, so not as much of an issue
- General feedback / review on OGC API - Features docs … like linking CQL2 docs
Gabe: Catalogue loader
- If gabe can get it in it would be very welcome (and not wait for another 6 month).

Release manager is Gabe and Jody:

Jody would like to start a bit early, and aim to release on the 18th, rather than start on the 18th.
Jody would like to ask user list to check nightly builds, on March 1st (usual release candidate day) as we have no release candidate.
- This would be very good feedback for catalogue if gabe can sneak it in, probably delay ask until we can get catalogue load feedback.

Glitches:

Website nightly build link is broken, likely
- geoserver.github.io/_config.yml at main · geoserver/geoserver.github.io · GitHub
- Andrea is looking at it
- main nightly is “release ma” - leave my mom out of it
Docker 2.27.x is not working
- Usually it is this script docker/build/release.sh at master · geoserver/docker · GitHub
- Any volunteer to look at it?

jive · February 26, 2025, 12:31am

The website fix is here: Fix up Nightly Nightly links by jodygarnett · Pull Request #247 · geoserver/geoserver.github.io · GitHub if anyone is available to review.

The docker issue was reported previously GEOS-11572 Docker main published as 2.25.x. I would like to see this fixed so we can ask for help testing ahead of 2.27.0 release.