GeoTools / GeoServer PMC meeting - 2025-04-08Attending -
Peter Smythe - Gabriel Roldan - Andrea Aime - Kevin Smith - Jody Garnett - Jukka Rahkonen Actions from previous meeting - [image: unchecked] Volunteer needed: postgis testing github workflow action - [image: unchecked] aaime: geoserver-release-docker add docker prune - check in next week to see if it’s working - [image: checked] Jody: make components mandatory - [image: unchecked] Torben: Ask on Dev list if others use components Agenda - GeoServer 2.27.0 - CITE Certification - GeoServer 2.26.3 release - GeoServer 3 Last Call - Workspace cloning and synchronization - Tracking admin user making config changes - var, lombok and more chit chat Actions - [image: unchecked] gabe: some small update for dev guide, updating conf.py by hand no longer needed - [image: unchecked] Discuss var and lombok next time GeoServer 2.27.0 GeoServer 2.27.0 is announced: - https://geoserver.org/announcements/vulnerability/2025/04/04/geoserver-2-27-0-released.html Socials: Please repost etc… - linkedin: https://www.linkedin.com/feed/update/urn:li:activity:7315110414604726272?utm_source=share&utm_medium=member_desktop&rcm=ACoAAABNvTABzdxJADBRGhR1XD6MPIb3YlMkTB4 - mastadon: https://fosstodon.org/@geoserver/114298616064233481 - bluesky: https://bsky.app/profile/geoserver.org/post/3lmatddi4mc2j - twitter: https://x.com/GeoserverO/status/1909348461759115637 - facebook: https://www.facebook.com/share/p/16SF9twSzH/ This ended up being a significant release! Thanks to everyone involved. - CITE certification was not ready quite yet, see below actions: - [image: unchecked] gabe: some small update for dev guide, updating conf.py by hand no longer needed How to make it less work to do a release? And still maintain option to build older archive branches… - Quick: Create main/stable/maintenance/archive jobs and just switch branches rather than creating new jobs. This implies we duplicate the last archive (2.25.x) job to create a new (2.26.x) job - Alternative: Make a Jenkins <https://www.jenkins.io/doc/book/pipeline/jenkinsfile/> file and check it into the source code for each branch. This would take a bit more work, the result is more similar to github workflows. - Simplify GWC release process - The xsdoc step has fallen out of use; perhaps this could be removed? - the XSD docs on sourceforge have zero downloads - The XSD also produces errors on GeoServer startup - Replace the ruby script with bash, or update from Ruby 8.7… (AI translation to Bash anyone?) - Jody has some ant scripts that could be adapted - Limit CITE certification to major release? Maybe only one a year to avoid undue costs - Trust github actions to “pass” for the dot releases - We may occasionally need a GeoServer 2.27.0.1 to pass if OGC is using older/newer CITE Team Engine CITE Certification Peter and OSGeo is working it. - OSGeo MOU says that that they can only so many “reference implementations” - https://www.osgeo.org/partners/ogc/ → - https://www.osgeo.org/wp-content/uploads/MOU_OSGeo_20081201.pdf - the link on the page is broken, sent a message to SAC chat Proposal to make use of funds raised for this activity; please respond. - https://discourse.osgeo.org/t/proposal-allocation-of-cite-certification-sponsorship-funding/145783 Certification progress tracking: https://git.osgeo.org/gitea/osgeo/standards-committee/issues/10 Actions: - [image: unchecked] Peter: Make the PR with live logo on home page, blog post etc… GeoServer 2.26.3 release Andrea volunteered, thanks. See release schedule: https://github.com/geoserver/geoserver/wiki/Release-Schedule GeoServer 3 Last Call News announcement: https://geoserver.org/behind%20the%20scenes/2025/04/08/gs3-last-call.html Socials: Please repost etc… - linkedin: https://www.linkedin.com/feed/update/urn:li:activity:7315405470460956672?utm_source=share&utm_medium=member_desktop&rcm=ACoAAABNvTABzdxJADBRGhR1 XD6MPIb3YlMkTB4 - mastadon: https://fosstodon.org/@geoserver/114298616064233481 - bluesky: https://fosstodon.org/@geoserver/114298616064233481 - X: https://x.com/GeoserverO/status/1909642037865107765 - facebook: https://www.facebook.com/share/p/1MamBW4bZw/ For discussion in the days ahead: - Start after easter! - Milestone 1: - ImageN is the big critical path item - OAuth2 is another example that can be worked on independently - These things can stay as 2.28-SNAPSHOT for September 2.28.0 - Milestone 2: - This is the point where 2.28.x ends and 3.0.x starts… - Do we take over main? After making 2.28.0 above? Or make a “devel” branch (which is nice for website home page which already provides such a thing for RCs) - Milestone 3 - everyone back in the pool - If you had a community module you love; now is the time to test + retain it Q: Expected timeframe - Milestone 1, Starts in May … - Milestone 2, starts when ready trying for 1-2 months crunch Q: What to tell people about contributing - Codebase is open for Milestone 1 - Locked down for Milestone 2, so important to keep this small Workspace cloning and synchronization To be disregarded as the customer’s withdrawn the request for support Tracking admin user making config changes Existing UI options show creation / modification time that is already recorded Proposal is also to record new information, the admin that made the change. - privacy aspect? track only when display is required … - right to be forgotten in europe; make a bulk change tool … - or reacts to removal of a user… - we do not get notified when user is removed in LDAP, so tool is perhaps preferable - Just the last modification… Who has rights? - global setting, env variable override is delayed… var, lombok and more chit chat delayed to next time
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
