...

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. https://github.com/fcrepo/fcrepo/pull/1988
   4. Semantic correctness?
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 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

6. Migration Report

Notes:

...

1. Today is Peter's last meeting (though he plans to "hang around a bit") – best wishes to Peter!

...

:

...

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

...

1. Should be able to begin release process next week

...

1. See link in committers channel; help with estimating time to complete outstanding tasks would be appreciated

...

1. Mike is working on FCREPO-3813; thinks this would be good for Calvin to test once ready

...

1. FCREPO-3815 is now on Mike's list and has been removed from here.

...

1. He will update tickets with latest findings.
2. He reports that he is sometimes getting an empty HTML report (this may be related to using --failure-only mode). Seems possible there is a bug here.
3. Will test migration work in PR next.

...