...

1. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

2. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

3. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

Minutes

1. a. fcr:backup/ fcr:restore will not in future API specification. b. Import/Export sprint planning will start tomorrow and the tooling is the future standard for Fedora backup and restore. At some future point, when resources permit, fcr:backup/fcr:restore will be moved out of the core codebase into a module in fcrepo-exts, with the accompanying changes in support guarantees. At some even later date, once it is clear that the new import/export based tooling accomplishes the same ends as fcr:backup/fcr:restore, fcr:backup/fcr:restore will be removed from fcrepo-exts entirely.

    

2. Fedora 4.6.0 doesn't have any blockers, the release candidate will out tomorrow morning. Looking for people in the community to test it - Release Testing - 4.6.0. Aaron Birkland will test windows.
3. If you have a running production Fedora 4 and would like to test the  fcr:backup/ fcr:restore on ModeShap 5, please do the testing

   Jira
   server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2069

    and report to Andrew Woods
4. All API spec document will be finalized as soon as possible. This effort will start immediately after the Import/export Sprint

...