2023-09-27 - Officially Supported Technologies

Owned by Craig McNally

Last updated: Nov 08, 2023Version comment

3 min read

Date

27 Sep 2023

Attendees

Discussion items

Time	Item	Who	Notes
1 min	Scribe	All	Ankita Sen is next, followed by Jakub Skoczen
10 min	Officially Supported Technologies	All	Postgres 12 EOL Fall 2024... Handle in Quesnelia page Quesnelia - Technical Council - FOLIO Wiki Typescript needs to be addressed Open question: Timelines Want to give people more lead time before the Poppy release Today: Check in on progress Florian Gleixner (postgres 13? 14? 15?) Jeremy Huff / Zak Burke (typescript) Lombok? MinIO/S3? Need to bring Quesnelia page up to date
*	Officially Supported Technologies - Upkeep	All	See 2023-06-21 Meeting notes for the most recent discussion notes on this the upkeep process. Options: Capture/document the ad-hoc process which we've been following in lieu of a having a formally defined process Go back to the previous meeting notes and try to resurrect the process we started to define (see link to meeting notes above) Do #1 now (short-term/stop-gap solution) and continue to try to make progress on #2 (longer-term solution) Considerations Relevant release milestones Expectations for the TCR process / Which list should we be looking at? How do we ensure this isn't a moving target for developers (both internal and external to the project) throughout the release cycle Do we need notification mechanisms for announcing changes to the OST list for the release in development? Implications on planning for the next release cycle Notes from today :
NA	Zoom Chat		Tod Olson to Everyone 11:08 AM Let the record show that the other thumbs up was from @Marc Johnson Maccabee Levine to Everyone 11:10 AM I would add the consideration, "which version of the list do we refer to when reviewing a TCR". Because the recently-released version is usually not worth testing against for a new module, but I think it's what we require now. Marc Johnson to Everyone 11:14 AM I think that’s the version in flight at the time of review Tod Olson 11:14 AM That seems right to me. Marc Johnson to Everyone 11:19 AM They only have to be late breaking because of decisions the community has made It’s not intrinsic to the challenge space Julian Ladisch to Everyone 11:27 AM Existing modules are free to upgrade dependencies whenever they want. New modules should also be free to either use the dependencies from either the latest released version or the next version. Tod Olson to Everyone 11:34 AM Aside: let's remember to save time to check progress on Postgresql, Typescript, etc. Tod Olson to Everyone 11:42 AM Looks like there are some changes in PG14 that affect some of the SQL functions. Julian Ladisch to Everyone 11:42 AM Which? Tod Olson to Everyone 11:47 AM Should we specify a JavaScript/ECMAScript version? Mark Veksler to Everyone 11:51 AM and with Kafka, should we say MSK? Marc Johnson 11:53 AM If we were to do that, we should also include Aurora etc I don’t think FOLIO has made an official stance on supporting AWS specific tooling Mark Veksler 11:53 AM Opensearch is mentioned Marc Johnson 11:54 AM It is, that was based upon explicit conversations about ES and OS AFAIK Open Search is not AWS specific Mark Veksler 11:55 AM it is a service from AWS it is ‘derived’ from ES Marc Johnson 11:56 AM It is, but it is not specific to AWS, even if it’s maintained by developers from AWS Julian Ladisch 11:59 AM AWS provides many open source software as a service. OpenSearch is open source licensed and can and is run without AWS at several institutions. Taras 11:59 AM Following the AWS documentation it should not be a big deal to upgrade to the latest major version of PostgreSQL https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion Marc Johnson to Everyone 12:01 PM My bad, about using Aurora as an example We need to decide what variations of our infrastructure we support

Action Items