february will have a two week sprints; polish the alphas, do a little more testing, prepare for beta release.
validation tool is still ongoing, but that should be finished soon.
Final plans for Beta release
Criteria – any questions?
targeted rebuild: the idea of being able to reindex a specific object; this is a future want, we need to create a more detailed list of things that need doing to be translated from the Jira into a prioritized list.
Timing – aim to finish the sprint at the end of february with a beta release in the month of february. plan is to have a validation tool sufficiently developed to help with migration process.
Existing Criteria: Scale, Response times under load, Migration rates, Performant S3 integration
Production Release Process
We have a small terraform project that will allow you to deploy fedora to the cloud using whichever database you use (but the suggestion is to use Postgres as that seems to be the most performant)
Danny Lamb has done testing with Islandora
Samvera is likely to align against Valkyrie since there seems to be no appetite in the community to upgrade ActiveFedora to work with Fedora 6.
Plan for the sprint is to look at reindex rates and identify what rates of reindex are. Can we compare these to the numbers we had from Fedora 4 when Stefano migrated and documented numbers.
Timing – shooting for a migration in June, but depends on the criteria, but the June is the hope.
Action Items
Danny Bernstein : consider creating a prioritized list of features for future development efforts using Jira as a jumping off point.
Danny Bernstein : create a page to collect data from the results of migrations (like a migration log). Some of this data already exists. would want information like time to migrate, time to build index.