| 5-10 min | Liaison Updates | | - CC: Maccabee Levine
- There was a presentation and discussion about AWS costs, which are significantly over budget. CC decided on an amount to limit the monthly spend, that ACRG or others would figure out how to achieve, and they are writing something up for clarity.
- They want to send out a detailed message, haven't done so yet.
- PC: Tod Olson
- Presentations on mod-marc-migrations and mod-record-specifications
- Voting ongoing, so far seems positive
- RMS Group:
- Security Team:
- Nothing special to report. Business as usual
- Tri-council Application Formalization:
- No meeting last week. Discussions about Eureka impacts as they surface.
|
| 25 min | Officially Supported Technologies (OST) | All | 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
Last week: - 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.
Previous Notes: |