Attending
Andrea Aime
Jody Garnett
Kevin Smith
Torben Barsballe
Actions from last meeting:- [In Progress] Torben: Write dependency backport details a bit more clearly in our developer guide
Agenda1. Getting ready for 2.19 release
-
gt-http client
-
Budget
-
Cleaning up modules: arcsde, s3-geotiff
-
XML cleanup
-
CITE tests update
ActionsN/A
Getting ready for 2.19 release
Looking at https://github.com/geoserver/geoserver/wiki/Release-Schedule
Marked down for March 1st, Jody plans to take a revision and setup the new branches and build jobs. Please get any changes in before this date 
-
Much improved with release bundling being part of the build checks now
-
Any community modules ready to be extensions?
-
Jody will check about geopackage again (waiting on customer interest, so if you care speak up)
-
Jody would like to remove gt-validation (it is already done from test clean up branch)
gt-http client
The pr is active:
-
Addressing split package issue last week
-
We want to get this ready asap as it’s blocking the other cleanup branches
Maven related build failures
Experiencing a number of failures due to Maven jar downloads.
Jenkins geoserver master failure, restarting, …
Mark/Brad already tried to reconfigure wagon-http for Azure, does not seem to be enough:
-
Disable connection pooling fully?
-
Shall we split the workflows so that we can restart one build at a time, e.g.: https://github.com/geotools/geotools/blob/master/.github/workflows/linux.yml
https://github.com/geoserver/geoserver/blob/master/.github/workflows/linux.yml -
We might be able to create a workflow template so that we can share configuration between workflows after splitting up: https://docs.github.com/en/actions/learn-github-actions/sharing-workflows-with-your-organization#creating-a-workflow-template
-
Not sure if this will actually work - it seems to be more aimed at sharing workflows between projects, but we may be able to adapt it to our needs
-
Small fix to ensure ~/.m2/repository used consistently applied to linux.yml, same needed for macos, and windows build should use what?
Budget
Budget request sent to OSGeo:
In general osgeo is providing less funds this year:
- Looks like 2k for projects that requested funds, 500 for those who did not email
Q: Should GeoCat end proposal for windows installer? A: yes
Cleaning up modules: arcsde, s3-geotiff, script
Already discussed about dropping arcsde support completely. → +1
JoshFix/GeoSolution “cog” improvements for image mosaic replacement is taking over from s3-geotiff. Can we remove s3-geotiff community module → yes
Remove gs-script as unmaintained.
XML cleanup
Mark proposed format cleanup proposed, similar to code cleanup.
-
Autoformat xml files
-
Yes: pom.xml and perhaps spring context files
-
No: xml schemas (use direct from ogc)
-
Proposed formatter does a dom based pretty print:
-
Get comments, but new-lines get removed
-
Use comments if we need to separate blocks of xml
-
Consider search replace multiple newlines with a comment
-
creates , tabs → 4 spaces
-
Try out eclipse formatter as an alternative
-
Would allow greater control, perhaps preserve newlines
CITE tests update
Believe we managed to pay GeoSolutions the remainder of the contract at the last day of 2020.
- Andrea will confirm
Scheduled to resume working on this next week.
Chit chat- varargs: https://github.com/geotools/geotools/pull/3317
-
Array of Object is fine - great!
-
Caution for array of primitives
-
Looks great for feature visitor
These are going to make for a great geotools release
-
Do we need to make a note in the update instructions?
-
Perhaps a code example
-
For inlined code examples the refactor will have already fixed them