One thing we missed from last week's missing, was asking for a volunteer for the release schedule <https://github.com/geoserver/geoserver/wiki/Release-Schedule>.
Release GeoServer 2.20.5 / GeoTools 26.5 / GWC 1.20.3 is planned for next week; is anyone available to make this release please. Aside: I tentatively updated the "release planning" to indicate GeoServer 2.22.x moving to Java version 11 and 17. Although this is waiting a proposal and PSC approval I thought it would be kind to advertise our intensions early for those planning ahead. -- Jody Garnett On Jun 7, 2022 at 10:24:24 AM, Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > GeoTools / GeoServer PMC meeting - 2022-06-07Attending > > - > > Torben Barsballe > - > > Jukka Rahkonen > - > > Kevin Smith > - > > Andrea Aime > > > Actions from prior meetings: > > - > > [DONE] Ian is working on GeoServer 2.21.0 release and announcement > > Agenda > > 1. > > Backport bot (and backport PR checklist?) > 2. > > Clean up on test code > 3. > > Build server migration progress > 4. > > GeoServer DNS management > 5. > > Code sprint > > Actions > > - > > Andrea to contact cholmes about DNS Zone Records for GeoServer > - > > Jody to reach out to Tom Ingold about the same(who Juan remembers > doing this last time) > > > Backport bot (and backport PR checklist?) > > Revival of an old backport bot that stopped working due to system changes > > QGIS has forked a version <https://github.com/m-kuhn/backport> of this > and kept it working for them > > Andrea has adapted the QGIS version and it seems to be working for > GeoServer > > The bot will create backport PRs automatically based on labels, e.g. > “backport 2.20.x” to create a backport targeting the 2.20.x branch. > > Note: The bot is still being tested, use with caution > > - > > Actions don’t appear to be run on backports. See > https://github.com/peter-evans/create-pull-request/issues/48 > - > > Requires a personal access token to be used > > Clean up on test code > > See email thread for details > > - > > Part 1: merged to main, not yet backported to 2.21.x > - > > move test dependencies to src/pom.xml > - > > short list test dependencies we like > - > > awaitity clean up (allows fast machines to exist when done, while > allowing build servers and slower machines more time) > - > > A few tests were waiting 30 seconds! > - > > note: Small effect on use of src/pom.xml as maven bill of > materials, the dependency management for the test frameworks will carry > over to "downstream" project including src/pom.xml > - > > Part 2: mock library dependency? We should choose one :) > - > > Easymock - alive, some trouble with Java 17 > - > > Mockito - also alive (far more popular), Java 17 happy, a bit nicer > to use / quicker to use (no need to write verify() each time) > - > > https://www.baeldung.com/mockito-vs-easymock-vs-jmockit > - > > Google trends comparison > <https://trends.google.it/trends/explore?q=easymock,mockito,jmockit> > > > > Build server migration progress > > - > > Plan: Move build.geoserver.org to larger server > > <https://github.com/geoserver/geoserver/wiki/Move-build.geoserver.org-to-larger-server> > - > > June 10th prep VM for transfer > - > > June 13th Purchase AX101 instance and transfer VM > - > > June 15th Verify builds and update DNS entry > - > > June 20th Restore jobs to were disabled to lack of space > - > > Juan has made a copy of the VM, converted to a different format > - > > Allessandro is going to try testing this in a new environment > - > > Purchase box and migrate after the test > > GeoServer DNS management > > We have the DNS, but not the zone record: > > - > > https://trac.osgeo.org/osgeo/ticket/2756#comment:1 > > > docs.geoserver.org: > > - > > https://trac.osgeo.org/osgeo/ticket/2640 > - > > Asks us to setup docs.geoserver.org website, before "resetup" the DNS > entries > - > > Copy geotools job format and credentials > > > Action: > > - > > Andrea to contact holmes > - > > done: Jody to reach out to Tom Ingold (who Juan remembers doing this > last time) > > > Code sprint > > Bolsena: > > - > > Costs have been reduced (due to OSGeo support and sponsorship) > - > > https://www.osgeo.org/events/bolsena-code-sprint-2022/ > - > > Idea: osgeo-api core and features cleanup? break up into modules > - > > review integration with spring mvc > - > > building links between resources > - > > not clear how to link - provide generic link without a format > and let content negotiation happen > - > > Idea: database table management via importer > - > > Mode for "create", "update" consider adding a mode for "delete", > see UpdateMode > > <https://github.com/geoserver/geoserver/blob/6e9e25c0c7cdda9ada9f33f8255130d3afc76801/src/extension/importer/core/src/main/java/org/geoserver/importer/UpdateMode.java#L13> > - > > Andrea indicates the REST API may have an option … nope. > - > > Check out how coverage's manages granules - parameter called > "purge" with "none", "metadata", "all". > - > > Idea: GSIP-202 Welcome Page Layout > > CITE code sprint: > > - > > not scheduled? We had hoped for June … > > > > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
