Versions Compared

Key

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

Date

...

TimeItemWhoNotes
1 minScribeAll

Jakub Skoczen is next, followed by Taras Spashchenko 

Taras will take notes today.  Thanks!

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.

1 minTCR Board Review

All

Nothing new today

5-10 minLiaison Updates
1 minUpcoming MeetingsAll
  • - Topic TBDOfficially Supported Technologies → Quesnelia: review and move to ACTIVE
  • - Cancelled
  • - Cancelled
  • - Cancelled
  • - Chairs Meeting (Tentative)
  • - Topic TBD - will likely cancel, but keeping as a placeholder in case something comes up
5 min

Technical Council Sub Groups Updates

All

Quick updates only.  If we can't find volunteers for groups, we'll need to add the topic to our backlog and address it during dedicated discussion sessions.

5 minRFCs

All


RFC Process Improvements:

  • We need another RFC to update the metadata retroactively to reflect the new or adjusted statuses.
    • Any volunteers?
    • Holding off on this for now - maybe someone will volunteer after the holidays.

Notes:

15-20 min

Postgres Messaging

All

From slack last Wednesday :

At today's meeting we discussed the communication plan for the postgres/quesnelia decision we made on Monday.  Please take a look at the draft message in the notes (2023-12-13 - Comms for Quesnelia Postgres) ahead of next Monday's meeting.  If you have any comments/suggestions please leave them inline right on the wiki page.  The plan is to finalize the messaging at our next meeting and get it out by EOD 12/18.

Notes:

.


Draft message:

  • PostgreSQL 12 will hit EOL as of November 14, 2024 and FOLIO needs to transition to a current version, PostgreSQL 16. The Quesnelia will be a transition release which must run under both PostgreSQL 12 and PostgreSQL 16, this will allow deployed environments to transition.
  • It is imperative that, when deployed environments switch from PostgreSQL 12 to PostgreSQL 16, nothing breaks due to this update.
  • For Quesnelia, modules should be constrained to PostgreSQL 12 features which are forward-compatible (not broken by) PostgreSQL 16.
  • Making this transition will have implications across the technical side of the project, and the The Technical Council will collaborate with affected audiences / stakeholders to assess any impact and potential implementation issues.

List of communication channels to share this message in:

  • #development
  • #sys-ops
  • #devops
  • #folio-product-council
  • #folio-community-council
  • #tech-council
  • #releases - at-mention Yogesh/Oleksii P.
  • #folio-implementers
  • #product_owners (private)
1 minDecision LogAll

Standing agenda item... is there anything in the decision log requiring attention?

*

Officially Supported Technologies

All

Standing agenda item to review/discuss any requested or required changes to officially supported technology lists

  • Check in on progress... does anything else require attention?

Quesnelia Officially Supported Technologies discussion:

  • React ^18.2 is correct (Zak Burke)
  • Zak Burke will check RTL support for React 18
  • Cypress ^9.1.1: Talk to the people who use it and find out what they would like to do
  • Update Grails from 5 to 6:
    • Craig McNally: I would rather make the statement that we need to go to 6; otherwise, the longer we wait and deliberate and evaluate and so forth that means it's less time for developers to do the actual work.
    • Marc Johnson: 100% completely agree

Moved to the next meeting:

  • Formalize decisions on the following.  Quesnelia is the last chance to upgrade to avoid running unsupported versions:
    • Postgres 13 → Quesnelia 
    • Grails 6 → Quesnelia
  • Postgres 15 → Ramsons
    • Wait until we see the result of Kitfox testing
  • Attempt to move Quesnelia from DRAFT → ACCEPTED → ACTIVE since the relevant milestones have already passed.
NAZoom Chat


...