- Tod Olson
- Mark Veksler
- Jakub Skoczen
- Craig McNally
- Marc Johnson
- Marko Knepper
- Vince Bareau
|25 min||Update on "Upgrades with Reference Data"||TC|
Last week's discussion ended with:
JIRA FOLIO DevOps sprint ticket to be added here
RE: discussion of immutable data - wondered if we have explicit flags (like isReadOnly) in the UI... don't think that exists.
1) Upgrades can fail and stop for reasons that aren't truly fatal
2) FOLIO Installation/upgrade comes with a data set that may need to differ for a given deployment since they'd customized that data set from a prior deployment - not a good way to understand/deal with this scenario
3) There is no way to flag data that a module requires as "immutable"
4) Upgrade shouldn't leave the system in an unusable state
Note that Craig surveyed FOLIO implementers and there wasn't a clean/consistent list of reference data. Suggestion to consult Anne L. Highsmith at TAMU. Christie Thomas at Chicago may also be a good resource.
Need a concrete list of what operational issues can be solved in the Honeysuckle release - would need a recommendation practically in July.
Need a Tech Council Champion. Stephen Pampell volunteered.
|15 min||Scratch environments for Dev Teams||Update on the work happening for the scratch environments|
|0 min||No meeting 6/17||announcement|
Many have conflict
|0 min||Architectural blueprint update 6/24||announcement||Monthly update of Architectural Blueprint items scheduled for June 24.|