...

1. Announcements
2. Pre 6.2.0 issues to resolve:

   1. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3819

   2. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3820

3. 6.2.0 Release Testing
   1.  Tickets Included
   2. Testing
      1. Release Testing - 6.2.0
4. Installed base information gathering option doc
5. Updates on mysterious bugs
   

   1. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3818

6. Updates on In Progress Tickets

   1. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3674

   2. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3673

   3. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3813

7. Tickets to be aware of
   

   1. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-38153423

   2. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-34233807

   3. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3807

   4. Jira
      server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3806

8. Migration Report

...

1. 1. 3806

2. Migration Report

Notes:

1. Announcements
   
   1. Today is Peter's last meeting (though he plans to "hang around a bit") – best wishes to Peter!
2. Pre 6.2.0 issues to resolve
   1. Jared has been working on FCREPO-3819 – he reports that the work wasn't horribly difficult, but he has some concerns about possible unexpected side effects caused by SPARQL manipulation. A PR is available for testing, but is it possible there's a better way? Should affected users fix their data, instead of having a long-term ongoing code change? (This problem should only impact users who started with an empty repo and populated it via API – not an issue for people coming in via migration-utils; could be fixed by a fairly simple external tool and might not even require a reindex). Peter pointed out that fixing the triples on disk will generate new OCFL versions, and would leave behind old versions with incorrect triples in them – though this is not necessarily a problem.
      1. Consensus: simple change and external tool is preferable to increasing code complexity in the core software.
      2. Suggestion: create an "OCFL Doctor" tool as a home for this kind of cleanup/checking/fixing functionality
         1. The tool could do a "dry-run" generating a report which could then be used as input for a "fix" run.
         2. Peter volunteered to get a start on this
   2. FCREPO-3820 did not require detailed discussion and is related to the above.
3. 6.2.0 release testing
   1. Should be able to begin release process next week
4. See link in committers channel; help with estimating time to complete outstanding tasks would be appreciated
5. Updates on mysterious bugs: no updates
6. Updates on in progress tickets
   1. Mike is working on FCREPO-3813; thinks this would be good for Calvin to test once ready
7. Tickets to be aware of
   1. FCREPO-3815 is now on Mike's list