...
- Announcements/Update
- v1.0.0 release of fcrepo-import-export
- v1.0.0 release of fcrepo-storage-ocfl?
- In the hopper: fcrepo-exts/migration-utils
- Docker-hub retention policy
- Planned Breaking Changes (standing topic)
- What we mean by "Beta": A proposal proposal - (Reference: 2020-10-28 - Fedora Leaders - Committers Meeting)
- Feature complete
- API test suite fails (Indirect Containers, State tokens, etc)
- Containment for Mementos
- Minimal Search Service UI
- Performant rebuild
- Side-loading / targeted rebuild
- Performant S3 integration (how to measure)
- Object Locking
- Session Rollback
- Performance criteria
- Scale
- Response times under load
- Migration rates
- Documentation
- Documented API compliance of Beta
- Documented missing features of Beta
- Documented breaking changes of Beta
- Documented upgrade process for Beta
- Other priorities
- Validation tool (F3->F6)
- Islandora integration
- Samvera integration
- Feature complete
- Next week's sprint
- Current pull-requests
Expand title Tickets resolved this week... Jira server DuraSpace JIRA jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
...
- v1.0.0 release of fcrepo-import-export
- Used for exporting from Fedora 5.x
- v1.0.0 release of fcrepo-storage-ocfl?
- Dependent on https://github.com/UW-Madison-Library/ocfl-java
- Dependent on the OCFL Editors approving https://github.com/OCFL/extensions/
- Dependent on https://github.com/UW-Madison-Library/ocfl-java
- In the hopper: release of fcrepo-exts/migration-utils
- Dependent on release of fcrepo-storage-ocfl
- Docker-hub retention policy
...
- Moving to a paid model and removing inactive containers
- Intended to be implemented Nov. 1
- Postponing for 6 months
- We may want to explore alternatives
What we mean by "Beta": A proposal A proposal
- Put out Alpha after next code sprint
- Need a bit more documentation
- Need releases for the various components of the migration tooling
- Pre-release binaries would also be fine
- Thoughts on beta proposal
- External tools and integrations don't need to block a beta test phase (but would block full release)
- Performance and scale
- How many objects do we want to demonstrate?
- How is response time performance impacted at scale?
- Migration rates - X objects in X time
- What is acceptable?
- 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
- General consensus on the call. Andrew will draft a full proposal and share with Leaders for buy-in
Next week's sprint
- Focus on docs for Alpha release
- A few clean-up tasks
- Progress toward Beta
- Danny planning on work on S3 support
Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3465 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.
...