2020-07-29 Meeting notes

spampell

Updates on latest thinking. Reviewed this discussion - conflict in existing and new reference data caused the upgrade to halt - and unsure as to what the state of the system was. There are 2 categories of data; one that shouldn't be changed by the functional users, and the second that needs to be there but should be allowed to be edited by such functional users.

Open questions in this post resulted in this wiki page.

Circling back to this issue, there are 2 key needs:

1) Need to handle the failure more gracefully - i.e. recoverable/restartable upgrade

2) Need to define "reference" data and determine how to handle mutable/unmutable sets.

These arguably stem from a missing architectural piece.

Recommendation is to take this conversation to the Tech Leads. Would need to include some framing/vision discussion/documentation and be very clear what we are asking them to do. Would benefit from having a "Product Owner" that can break the problem down into composite stories (analogy drawn between this task and the "Scratch Environments"). Can't ask teams that deal with this to do it "on the side" - should be assigned and acknowledged as part of their resource assignments.

spampell and Marko Knepper have volunteered to assume the "Product Owner" role; clarify the problem and to break down the needs and potential approaches - goal is to deliver something of use for Q4.

 Discuss question posed in this issue:  FOLIO-2708 - Getting issue details... STATUS

VBar

Mike Gorrell