...
Camel component issue - priority for next week's workshop
Next release planning
- Switching to a new conference line
- Notes from the field: HydraConnect
- Issues raised:
Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1742 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1754
- Constructive interop discussions: best practices and common us of PCDM
- F3 to F4 migration interest group
- Issues raised:
- Scale/performance opportunities – brainstorm testing scenarios
- Vagrant refactoring: new base-box?
Landing in-flight issues - revisited
Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13202 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 - ...
...
Let's say we do that...which modules to be released (not a huge deal)
Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1752 Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1706 Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1683
It was suggested in a previous release that release candidate branches be created
Let these float out there for testing (as integration tests alone may not be sufficient)
Are people in the position to do sandy sanity testing (if candidate branches created over the next week)?
Ideally, all developers in Fedora who run into issues while testing would create a ticketFor example, the most Vagrant issues (tests are passing, but not working)
...