...

1. Put out Alpha after next code sprint
   1. Need a bit more documentation
   2. Need releases for the various components of the migration tooling
      1. Pre-release binaries would also be fine
2. Thoughts on beta proposal
   1. External tools and integrations don't need to block a beta test phase (but would block full release)
   2. Performance and scale
      1. How many objects do we want to demonstrate?
      2. How is response time performance impacted at scale?
      3. Migration rates - X objects in X time
      4. What is acceptable?
      5. Performance and scale benchmarks shouldn't block a beta release, but we should be able to support all the relevant tests during the beta phase
   3. General consensus on the call. Andrew will draft a full proposal and share with Leaders for buy-in

Next week's sprint 

1. Focus on docs for Alpha release
2. A few clean-up tasks
3. Progress toward Beta
4. Danny planning on work on S3 support

5. Jira
   server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3465

6. Jira
   server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3192

Actions

•  Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-08-13- Fedora Tech Meeting)
•  Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-08-13- Fedora Tech Meeting)
•  Who:  Clarify in documentation that multiple simultaneous writes to OCFL are not supported
•  migration-utils - translating RELS-EXT/INT into RDF in Fedora 6: is the functionality there? If not, add it.

...