Ticket for certain monitoring https://trac.osgeo.org/osgeo/ticket/3357 - - Jody Garnett
On Feb 25, 2025 at 10:28:23 AM, Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > GeoTools / GeoServer PMC meeting - 2025-02-25Attending > > - > > Torben Barsballe > - > > Jukka Rahkonen > - > > Peter Smythe > - > > Kevin Smith > - > > Gabriel Roldan > - > > Andrea Aime > - > > Jody Garnett > > > Actions from prior meetings: > > - [image: non selezionata] > > 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: non selezionata] > > 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: non selezionata] > > Jody: Motion to direct prior funds generated for CITE certification to > direct towards Andrea, Peter, Gabe, and those who contributed as > appropriate. > - [image: non selezionata] > > Peter: Add notes to developers guide on how to make this repeatable > - [image: non selezionata] > > Andrea: Clean up CITE build server jobs that are not in use please > (done) > > CITE tests updates > > Help requested from OSGeo: > https://git.osgeo.org/gitea/osgeo/standards-committee/issues/10 > > WMTS 1.0 fixes: > > https://github.com/geoserver/geoserver/pull/8175 > > Need to get two fixes merged before we can get it work with production TE: > > - > > https://github.com/opengeospatial/ets-wmts10/issues/98 > - > > https://github.com/opengeospatial/ets-wmts10/issues/99 > > > 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 > > <https://github.com/geoserver/geoserver/blob/main/build/cite/run-test.sh#L139> > possible > - > > GeoTIFF testing > > <https://github.com/geoserver/geoserver/blob/main/build/cite/run-test.sh#L139> > 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. > > https://letsencrypt.org/2025/01/22/ending-expiration-emails/ > > Suggestions: > > - > > monitoring service - Red Sift > <https://redsift.com/pulse-platform/certificates-lite> > - > > 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 > - > > > https://github.com/geoserver/geoserver.github.io/blob/main/_config.yml > - > > 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 > https://github.com/geoserver/docker/blob/master/build/release.sh > - > > Any volunteer to look at it? > > _______________________________________________ > GeoTools-Devel mailing list > GeoTools-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel >
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
