GeoTools / GeoServer PMC meeting - 2025-11-04
Attending
- Torben Barsballe
- Cécile Vuilleumier
- Kevin Smith
- Jody Garnett
- Peter Smythe
- Gabriel Roldan
Actions from prior meetings:
- None
Agenda
- GS3 Code Sprint Update / Code Thaw!
- Website Communication
- Community Publish
- mkdocs update
Actions
- All: Test out the GeoServer 3.0 Nightly build
- Gabe: Release 2.28.1
GS3 Code Sprint Update / Code Thaw!
The sprint exceeded expectations! Nightly build is running.
Spring updates were a bit of a challenge, required notable rewrites throughout web interfaces
Some challenges with downstream apps:
- MapFishPrint is stuck on v2. Explored options for upgrading:
- Integrate into GeoServer as a library
- Donate to GeoTools (requires License change)
Next step: Testing! Try out the nightly build binary and report any bugs.
- Peter: testing!
- Todo: need to test and write docker install instructions with |version| and |release| examples
|release| example:
.. parsed-literal::
docker pull docker.osgeo.org/geoserver:|release|.x
- Work resumes on OIDC after code freeze
- ImageN feedback and test coverage resumes after code freeze
Some doc updates have been made to improve installation experience of extensions.
Likewise, the first example of the community module publish profile (OpenSearch) has been added - more to come!
- Cecile: httpclient 5 client update in geotools, to match GeoServer
- OpenRewrite did some of the work, and the correct some stuff, or failed QA due to deprecations. Been merged today! Congrats and thanks to Daniele
- Gabe:
- Looking forward to Milestone 3 ACL and GeoServer Cloud
Blog:
- Intend to publish this today?
Website Communication
- Pending community modules, are now shown on nightly builds!
- For release we will link to SF Download
- peter: Some challenge to communicate that SNAPSHOT = nightly build
- Updates to contributors page and “security” tag for the commercial support page- please comment on the Discourse thread.
Community Publish Pending
Community publish GSIP is “done”:
- See website nightly build example
- New profiles and stuff
- See developer guide for care and feeding of pending release profile
mkdocs update
The “translate” script:
- pandoc and then cleans up the mess
- for custom “rst” directives invented by sphinx: downloads, inline code, and so on …
github action so that any commits get built and put them on github pages:
- Live preview: http://geoserver.org/geoserver/
- https://github.com/geoserver/geoserver/pull/8876 has updates each time it builds
- PR is now out of draft!
- Pandoc was old version of ubuntu action
- label “mkdocs” then the mkdocs publish, and report back on PR success
- So any PR can do this
- So you can only actually see the last PR publicly
- A bunch of warnings and so on to fix up
- broken reference etc…
What is next?
- review and commit the fixes we have now
- cycle to fix warnings with subsequent PRs using “mkdocs” label to preview
Q: Can we actually convert the developers guide? For example …
- This would change developer guide form RST to MD
- warnings: can fix in RST, or after the fact in markdown
Q: Can we get this transition during “GS3 Milestone 2”?
- Gabe: that would be great
Notes about config.py changes:
- release - this is now the most recent release to use in download examples and links
- version - this is now looked up from src/pom.xml directly, so nightly build or release (when on tag)
ChitChat
Release in two weeks time? 2.28.1
- Gabe volunteers
- Jody can support with an ImageN release (if needed)
Q: Do we need to update release instructions for ImageN?
- No treat like mapfish print and ImageIO-Ext, something to sort out with a PR before release
- We do not wish to release with any SNAPSHOT jars
- GeoTools uses 0.9.0 right now so no change needed
- If we address the the JAI vs ImageN conflict Jody can make a 0.9.1