2020-09-09 Meeting notes

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.

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)