Versions Compared

Old Version 4

changes.mady.by.user Jenn Colt

Saved on

compared with

New Version 5

changes.mady.by.user Jenn Colt

Saved on

Key

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

...

TimeItemWhoNotes
1 minScribeAll

Ankita Sen is next, followed by Jakub Skoczen - Jenn Colt will take notes since they're both absent.

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. 

*Officially Supported Technologies  (Ramsons)All

Goal:  Move the Ramsons OST page from DRAFT → ACCEPTED.  Our (self-imposed) deadline for this is  

  • Review comments
  • Review/discuss the policies attributed to each section
  • Add/remove/change versions as needed (focus on 3rd party dependencies)

Notes:

  • Front end - policy asks for versions but right now we don't list them. We might list one or more versions, probably one (most cases will just support one version at a time but policy allows wiggle room if needed)
  • Might want to defer policy discussion in favor of settling on Ramsons requirements
    • Keep policy information for next release but remove for Ramsons
    • Stay with standards for previous releases
  • Frontend hasn't had versions previously so holding off on that for now
  • Node and Yarn - Node needs to get upgrade because of EOL concern, no plan for Yarn yet
  • First party -  skip until later in cycle
  • Shared - stay the same
  • During build automation testing- TBD, Craig McNally will talk to John Coburn and others
  • Post build testing - our Cypress version is old, people would like to upgrade to something beyond 10, these tools aren't as relevant for system operators, held in one repo so less coordination. Craig McNally will circle back with Zak Burke
  • Languages - Think Java is safe at 17 for now. Groovy not changing, open api not changing
  • Build tools -
  • First party - out of scope for today
  • Third party - Dependent on the support periods, suggest using latest available instead of specifying versions? Some disagreement about not specifying. Need to discuss the policy for these further because our first party tools are coupled to these third party tools. For Ramsons since not working on policy piece yet, extrapolating that there will be a 3.3 in time for Ramsons.
    • Hard to predict some of this without knowing release schedule. Spring boot periods support periods don't conveniently work with FOLIO so doing the best we can
    • Spring framework - good with 6.1
    • Grails - 6, k-int migrating now, will let TC know if it's an issue per Owen Stephens in a previous meeting
    • vertx - fine with 4, supported for 2 years after 5 comes out (not out yet)
    • Lombok - doesn't need to be consistent across modules
    • AWS SDK - needs to be 2 because 1 is reaching end of support
  • Build automation testing
    • uncontroversial for JUnit 5, rest assured is not cross cutting, testcontainers rely on version of docker but we aren't versioning docker so it's better not to try and version
    • these areas a bit frozen right now due to resourcing
  • Post Build Integration Testing
    • haven't specified versions in the past, all in one repo, so whatever version in that repo
  • Infrastructure
    • Postgresql 16 and only 16 is correct
    • Open Search 2 is what's available, ES 8 good at least until 9 is out, which it isn't. Maintenance periods may end up not coinciding well with FOLIO releases. Leave alone for now.
    • Kafka/MSK- Kafka should be a supported version of 3? haven't specified in the past, not ready to specify today, again schedule doesn't work well with FOLIO's
    • S3/MinIO - same
      • Will work on for Sunflower
NAZoom Chat


...