Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

Discussion items

TimeItemWhoNotes
1 minScribeAll

Florian followed by Marc

Reminder:  Please copy/paste the Zoom chat into the notes.  If you miss it, this is saved along with the meeting recording, but having it here has benefits.

5-10 minLiaison Updates
  • CC: Maccabee Levine
    • No CC meeting this week.
  • PC: Tod Olson
    • UPDATE (2024-09-12): mod-marc-migrations and mod-record-specifications approved by PC
    • Presentation on Reading Room functionality, spurred by LoC but may meet other use cases; primarily revolves around authorization to enter physical spaces.
  • RMS Group:
    • No updates
  • Security Team: 
    • Nothing special to report.  Business as usual
  • Tri-council Application Formalization:  
    • No meeting last week. Finalizing WC presentation this week.
1 minUpcoming MeetingsAll


  •  - Regular TC Meeting
  •  - Dedicated discussion: Continuation of architectural decision-making discussion
  •  - Cancelled: WOLFcon
  •  - Cancelled: WOLFcon
  •  - TC & WOLFcon
  • - Regular TC Meeting - include DA update
  • - Dedicated discussion: Static code group?
5 minTCR Board ReviewAll
  • ui-reading-room still under evaluation
  • mod-record-specifications: Ingolf Kuss:
    • dependencies on snapshot versions during development: should be discussed, if this requirement should be reformulated
    • API endpoint ...sync has to be changed
    • Ingolf wants to deploy the module to check the API, but without success at the moment
    • Some other open points
    • Marc Johnson: No need to vote when there are outstanding topics
    • Jenn Colt: we can vote offline too
    • Jeremy Huff: If modules are build the usual way, we do not need to re-check things, that are done by the folio libraries.
    • Maccabee Levine: Restrictions to snapshot versions - there is a open PR that we should discuss before accepting the module
    • Ingolf will talk to the team which expects a answer today.
  • mod-marc-migrations
    • Meeting with the development team had scheduling problem. Will meet this week hopefuly
    • PC approval last week
5 min

Technical Council Sub-Groups Updates

All



1 minRFCs

All

Reminder(s)

  • Review of open items, such as the need for decision log records and the application of the "Go" RFC.
    • Still need merge and decision log entry
1 minDecision LogAll

Need to log decisions for the following:  (see above)

25 min

Officially Supported Technologies (OST)

All

still open:

  • Java 21 discussion from the DevOps perspective. - believe we have capacity confirmation, should know by end of day Sept 16th.
    • Waiting for devops answer to upgrade Jenkins images to Java 21
  • Vertex.5 - we will wait for the capacity discussion
    • We stay on Vertex 4 for Sunflower and go to Vertex 5 on Trillium

Last week:

Check Recurring Calendar...

  • Spring Boot 3.4 (and Spring Framework 6.2)
    • Today RMS group has made the decision, see Liaison Updates section above.
  • Sunflower
    • The Spring Boot support period of 12 months for a single minor release has the same length as FOLIO's support period of ~ 12 months, however, these periods usually don't align.
    • Regarding Backend "First Party Libraries / Frameworks": A library/framework needs to support only one of the versions allowed in the "Third Party Libraries / Frameworks" list. This should be clarified in the description.
    • Adding folio-s3-client to first party libraries and the AWS and MinIO clients to third party libraries. folio-s3-client is an abstraction for the AWS and MinIO client.
    • Java 21
      • No objections from developers, the migration from 17 to 21 will be easy, simply bump the folio-java-docker image in the Dockerfile and the jenkins-slave-docker image in the Jenkinsfile.
      • Need to contact DevOps whether they can provide a Java 21 version of folio-java-docker and jenkins-slave-docker before the Sunflower development starts; recent commits (folio-java-docker history, jenkins-slave-docker history) have been made by David Crossley, John Malconian, and Julian Ladisch.
        • Craig McNally is reaching out to Mike Gorrell to see if there is capacity in time for Sunflower.
        • If yes, next step will be to create a ticket for DevOps
    • Vertx 5
      • Major release, some changes to how callback, futures, etc.; may affect how we chain things.
      • Julian has tried and found little difficulty with RMB
      • Arguments for holding off until Trillium, not want to upgrade both Vertx and Java, but signal this is coming
      • Note: Trillium expected in Fall '25, assuming no delays; Sunflower needs support for two releases, gets very close to end of Vertx 4 support if there are delays.
      • Current inclination is towards Sunflower, but not solid decision
    • For Java 21 & Vertx 5: will wait for Java 21 capacity conversation, make decision next week.
    • S3/MinIO - S3 API version: still need version, see Action Item below

Previous Notes:

  • Java 21
    • Recap:
      • No objections from developers, the migration from 17 to 21 will be easy. (See above.)
      • Need to contact DevOps whether they can provide Java 21 environment as above.
    • Actions
      • Craig McNally is reaching out to Mike Gorrell to see if there is capacity in time for Sunflower.
      • If yes, next step will be to create a ticket for DevOps
      • Note: KeyCloak has already deprecated support for Java 17 and will remove in next version. Support KeyCloak through a Bouncy Castle library. Bouncy Castle support for Java 21 does not mesh well. KeyCloak is aware, could possibly adjust.
  • Vertx 5
    • Major release, some changes to how callback, futures, etc.; may affect how we chain things.
    • Julian has tried and found little difficulty with RMB
    • Arguments for holding off until Trillium, not want to upgrade both Vertx and Java, but signal this is coming
    • Note: Trillium expected in Fall '25, assuming no delays; Sunflower needs support for two releases, gets very close to end of Vertx 4 support if there are delays.
    • Current inclination is towards Sunflower, but not solid decision
  • For Java 21 & Vertx 5: will wait for Java 21 capacity conversation, make decision next week.
  • S3/MinIO - S3 API version: still need version, see Action Item below
  • OpenSearch 2 & Elasticsearch 8:
    • Some differences have crept in.
    • FOLIO currently uses only the basic features thought the OpenSearch client that are available in both.
    • Marc Johnson has run into some more basic issues with Elasticsearch client in another project, more strict.


NAZoom Chat


No chant

...