[Geoserver-devel] GT/GS/GWC PMC/PSC meeting notes, January 5th 2021

GeoTools / GeoServer PMC meeting - 2021-01-05Attending

Actions from last meeting:

   -

   [DONE] Jody: Start email PSC vote this year to pay out of our 2020
   budget for CITE test contract, and then send authorization to treasurer
   when work is complete
   -

   [DONE] Jody: Will write it up as a proposal library/gt-http and
   plugin/gt-http-components and send it to email for vote?
   -

   Alessandro: Make a PR against geoserver/docker to start this repository
   going

Agenda

   1.

   OSGeo 2021 budget
   2.

   JTS 1.18 backport clarification
   3.

   JUnit 3 migration and PMD on tests
   4.

   gt-http proposal
   5.

   Java 11, Java 17, when do we drop Java 8?

Actions

   -

OSGeo 2021 budget

Some great ideas from the last meeting, we did manage to pay GeoSolutions
with our 2020 budget. We did not get approval on the email list for 2020
budget…

Board requests a budget July 17th:

   -

   Draft: https://wiki.osgeo.org/wiki/GeoServer_Budget_2021

Sidebar:

   -

   How to rent a macOS build machine? AWS now provides an option …
   -

      An on-demand option could substantially mitigate costs, since we only
      really need this 2 h every month or so (assuming we just want builds and
      not ongoing integration tests)

JTS 1.18 backport clarification

A good discussion based on the recent JTS 1.18 update.

   -

   Want to be careful that we only backport additions that respect the API
   -

   Recent JTS 1.18 upgrade:
   -

      removed a couple of “internal” public classes (which would be fine…)
      -

      but also had a change where buffer(0) was required (so no backport…)
      -

      … this is a feature release (so no backport).

Internally:

   -

   Updating for bug fix / security issues can be backported no problem…
   -

      Security fix may need to force an api change (it happens)
      -

   New functionality that does not require api change backport after a month
   -

      Some care can be done for additive changes that do not break binary
      compatibility

GeoTools should these guidelines also external dependencies? Since
downstream projects get these via transitive...

Action:

   -

   Torben: To write the above a bit more clearly in our developer guide

Sidebar:

   -

   Encouraging JTS to issue more patch releases :slight_smile:

JUnit 3 migration and PMD on tests

Have you seen the emails :slight_smile:

   -

   Great hopes on automation, but failed when test extended another test …
   -

   Discovered PMD not running on test sources (required a flag), turning
   that flag on destroyed happiness :slight_smile:

Are these ready to merge?

   -

   They are boring to review …
   -

   Merge all three together

gt-http proposal

See proposal: https://github.com/geotools/geotools/wiki/HTTPClient-Factory

Please vote, want to get this in before code cut off?

Feedback:

   -

   CommonFactoryFinder? Or use an HTTPFactoryFinder (for standalone …).

   -

   Similar to logging this could be independent … Log4J upgrade anyone?

Java 11, Java 17, when do we drop Java 8?

Going to be really tough to drop Java 8 :slight_smile: Many projects have not made it
to Java 11 yet …

   -

   Java 8 supported longer than Java 11 according to AdoptJDK

Java 11

   -

   gt-http proposal wanted to use new java internal http client
   -

   Java 11 specific module?

Java 17 is due in 2021 September:

   -

   records, long strings, …
   -

   JTS Coordinate … we could lay the ground work in JTS 1.19 and then go
   for an Unsafe / Java 17 combo :slight_smile:

Expectation:

   -

   Expect we will end up moving to supporting LTS with Java 8 / Java 17 at
   some point when Java 11 is dropped?
   -

   Java 8 / 11 / 17
   -

   Java 8 / 17
   -

   At some point ImageN - to get around com.sun image stuff