...

1. Announcements/Update
   1. v1.0.0 release of fcrepo-import-export
   2. v1.0.0 release of fcrepo-storage-ocfl?
   3. In the hopper: fcrepo-exts/migration-utils
   4. Docker-hub retention policy
2. Planned Breaking Changes (standing topic)
3. What we mean by "Beta": A proposal proposal - (Reference: 2020-10-28 - Fedora Leaders - Committers Meeting)
   1. Feature complete
      1. API test suite fails (Indirect Containers, State tokens, etc)
      2. Containment for Mementos
      3. Minimal Search Service UI
      4. Performant rebuild
      5. Side-loading / targeted rebuild
      6. Performant S3 integration (how to measure) 
      7. Object Locking
      8. Session Rollback
   2. Performance criteria
      1. Scale
      2. Response times under load
      3. Migration rates
   3. Documentation
      1. Documented API compliance of Beta
      2. Documented missing features of Beta
      3. Documented breaking changes of Beta
      4. Documented upgrade process for Beta
   4. Other priorities
      1. Validation tool (F3->F6)
      2. Islandora integration
      3. Samvera integration
4. Next week's sprint
   1. Current pull-requests

5. Fedora 6 Testing

   Expand
   title Tickets resolved this week...
   Jira server DuraSpace JIRA jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

...

1. v1.0.0 release of fcrepo-import-export
   1. Used for exporting from Fedora 5.x
2. v1.0.0 release of fcrepo-storage-ocfl?
   1. Dependent on https://github.com/UW-Madison-Library/ocfl-java
      1. Dependent on the OCFL Editors approving https://github.com/OCFL/extensions/
3. In the hopper: release of fcrepo-exts/migration-utils
   1. Dependent on snapshot release of fcrepo-storage-ocfl
4. Docker-hub retention policy

...

1. 1. Moving to a paid model and removing inactive containers
   2. Intended to be implemented Nov. 1
   3. Postponing for 6 months
   4. We may want to explore alternatives

What we mean by "Beta": A proposal proposal

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)
•  Danny Bernstein document the process of migrating from 4 → 5 → 6
•  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.
•  Danny Bernstein to organize a special topic call around the topic of high availability.

...