GeoTools / GeoServer PMC meeting - 2025-03-25
Attending
- Torben Barsballe
- Peter Smythe
- Gabriel Roldan
- Andrea Aime
- Kevin Smith
- Cécile Vuilleumier
- Jody Garnett
Actions from prior meetings:
- [image]Jody/Torben: Test geoserver-builds discourse email with Jenkins build notifications
- [image]Peter: Will remove unloved community modules (pom.xml, docs, packaging)
- [image]Gabe & Jody: Delay the 2.27.0 release (send new date to developer forum)
- [image]Jody will ask developers / community to test night builds for community data dir loader.
- [image]Jody: Meeting invite to geoserver-security list for a meeting next week at this same time
Agenda
- Jenkins Maintenance
- GeoServer 2.27.0 release updates
- Do we need to keep track of modules in Jira
- CITE testing activity update
- GeoServer 3
- Chit Chat
Actions
- [image]Volunteer needed: postgis testing github workflow actionvolunteer
- [image]aaime: geoserver-release-docker add docker prune - check in next week to see if it’s working
- [image]Jody: make components mandatory
- [image]Torben: Ask on Dev list if others use components
- [image]
Jenkins Maintenance
Some item came up during maintenance that have wider applicability to the PSC
- PostgreSQL 12 is obsolete (not supported/available on current OS version) - Used by GeoTools DB tests
Upgrade to 14 (or newer?).
But also, GitHub actions are using 11
Q: Do we advertise a minimum version of PostgreSQL?
- Dialect detects a few differences to for SQL generation
- Some features require PostgreSQL 12
Q: Do we want to advertise a minimum version?
- We would need to test if we establish a minimum
- Could set up a workflow matrix …
- Test from 11 to 17
- carbon footprint, consider full matrix on “main” rather than each PR …
- Tests are moderately heavy (5 mins to run)
- We are low on space on build server?
Prune unused docker: 5GB → 80GB
- Consider auto run docker prune
- geoserver-release-docker [Jenkins] runs frequently, maybe just tack on prune to the end of this?
- With CITE test images gone it may be lighter
docker system prune --filter “until=168h” -f (older than one week)
- Build failure sent message to discourse and it did not show up in discourse
- Jody has asked in SAC channel for help; but unclear what needs to change
action:
- postgis testing github workflow action is interesting if we have a volunteer
- aaime: geoserver-release-docker add docker prune
- Check in again next week to confirm this is working
GeoServer 2.27.0 release updates
-
Public testing has shown some glitches and troubles but is mostly good!
-
catalog load race condition:
docker run -it -p8080:8080 \ welcome-global-services-disabled
–env INSTALL_EXTENSIONS=true \
–env STABLE_EXTENSIONS=“ysld,ogcapi-features” \
docker.osgeo.org/geoserver:2.27.x
- Resolved with “–env GEOSERVER_DATA_DIR_LOADER_ENABLED=false”
25 Mar 16:34:07 ERROR [config.datadir] - Error preloading org.geoserver.util.EntityResolverProvider
org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘geoServer’ defined in URL [jar:file:/usr/local/tomcat/webapps/geoserver/WEB-INF/lib/gs-main-2.27-SNAPSHOT.jar!/applicationContext.xml]: Cannot resolve reference to bean ‘catalog’ while setting bean property ‘catalog’; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name ‘localWorkspaceCatalog’: Requested bean is currently in creation: Is there an unresolvable circular reference?
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:342)
Here is pastebin: https://pastebin.com/hHyFEfuk
-
Reduced community modules
Thanks Peter! -
jody: Could not reproduce the “service capabilities” when disabling global service.
-
Some problems with CSP so docs were “improved” with warnings.
Upgrading existing versions — GeoServer 2.27.x User Manual -
We also have a new Draft PR by Steve to handle feedback from CSP testing
-
We had our CVE round up and are organized for release
Availability:
- Gabe: Will look at the race condition above
- Jody can start on draft blog post today, and ask for team review editing
- Gabe: Monday for release artifacts
- Peter: On hand Monday for CITE testing
Do we need to keep track of modules in Jira
-
Jody spammed a bunch of people, by updating the tickets with no “component”
-
This is just by the release announcement script “vulnerability” and “community”
-
Could we make it mandatory? Yes we could …
-
Could we make it simple?
components simple: “geoserver”, “extension”, “community”, “vulnerability” -
Maybe raise with dev list
-
Ideally we could move github issues
e.g. GitHub - doctrine/jira-github-issues: Scripts to migrate Jira to Github issues, GitHub - hbrands/jira-issues-importer: Python scripts for importing JIRA issues in XML format into Github Issues
Actions:
- jody: make components mandatory
- torben: Ask on Dev list if others use components
CITE testing activity update
Peter:
- Waiting on 2.27.0 release artifacts!
Andrea:
- We are now passing WCS 2.0 build!
- passes on patched tests
- depends on Team Engine 6
- So we pass “eventually”…
- Jeroen: We have email indicating we can link to these issues when requesting certification
Jody:
- The website home page:
GeoServer implements industry standard OGC protocols - We will make a pull-request adding the stickers saying:
- “certified” for WFS, WCS, etc…
- “implementing” for WPS (that does not have a CITE test and cannot be certified)
GeoServer 3
- We are at 90%, please promote!
Jody would like to start
Chit Chat
Have a good release everyone!
