2020-09-09 Meeting notes

2020-09-09 Meeting notes

Date

Sep 9, 2020

Attendees

  • @Mike Gorrell

  • @Zak_Burke

  • @Marko Knepper

  • @Mark Veksler

  • @Ian Walls

  • @Tod Olson

  • @Jakub Skoczen

  • @Craig McNally

  • @Marc Johnson

  • @spampell

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

 

Review Tech Debt Kanban Board, assign actions

TC

Discuss the Tech Debt Kanban board, configuration, and review process. Make changes to issues, assign followups.

https://folio-org.atlassian.net/secure/RapidBoard.jspa?rapidView=169

Note - Open question about GDPR and whether there are Tech Debt items relating to it. More investigation/discussion to follow.

 

Review Release numbering Policy in light of dropping Quarterly releases

TC 

This process was approved earlier this year. Now that the project has agreed to move to 3 releases per year the Q nomenclature in the release numbering doesn't make sense. What is the TC's recommendation for new numbering of maintenance releases?

WAS: 

Release Numbering:

  • LTS Release numbering: YYYY-MM.S-LTS, where:

    • YYYY = Year

    • MM = Month

    • S = sequence/number of releases with the YYYY-MM tag

    • LTS = Long Term Support release

  • Quarterly Release numbering: YYYY-qN.S, where:

    • YYYY = Year

    • N = Which quarter during the year the release happens (1,2,3,4)

    • S = sequence/number of releases with the YYYY-qN tag

  • Flower names

    • When necessary/helpful flower names can be appended to the release number, i.e. 2020-q3.1 (Honeysuckle)

 

CHANGE TO:

Release Numbering:

  • LTS Release numbering: YYYY-MM.S-LTS, where:

    • YYYY = Year

    • MM = Month

    • S = sequence/number of releases with the YYYY-MM tag

    • LTS = Long Term Support release

  • Maintenance Release numbering: YYYY-N.S, where:

    • YYYY = Year

    • N = The Nth maintenance release that year (1,2,3,4)

    • S = sequence/number of releases with the YYYY-N tag

  • Flower names

    • When necessary/helpful flower names can be appended to the release number, i.e. 2020-q3.1 (Honeysuckle)

 

Optimistic Locking Update

@Jakub Skoczen

Update on discussions related to Optimistic Locking - Spike to discuss protocols and implementation specifics (in RMB). Will run design/proposal by Tech Leads.

 

Question on Distributed Config/Secrets Management

@Craig McNally

Security group ranked Authentication redesign as a higher priority, but what is the process for getting this on the official roadmap. @Mike Gorrellto raise this with Cap Planning team next Monday.

 

NEXT WEEK

 

Architectural blueprint updates