...
Announcements
- 5.0.2:
Release manager: Yinlin Chen
Date: February 6th
- Release Testing - 5.0.2
Ecosystem release/development policy review
- Status on current tools:
- fcrepo-camel and fcrepo-camel-toolbox toolbox release
- 4.7.3 release? (compatible with Fedora 4.7.x)
- fcrepo4-vagrant
- fcrepo4-docker
- Please review this PR: https://github.com/fcrepo4-labs/fcrepo4-docker/pull/35
- fcrepo-camel and fcrepo-camel-toolbox toolbox release
- Next steps for import/export/4→5 migration
- Proposal: Two pronged attack
- round-tripping 5.x data (add support for versions and webacs)
- fcrepo-migrate: transform 4.7 export into 5.x export
- A starting list of Jiras
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2979 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2980 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2981 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2982 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2983 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2984 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2985
- Proposal: Two pronged attack
- 5.1.0
- Ready for review
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1889 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2937 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2936 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2935 - "Check if metadata is available in commons.js" : https://github.com/fcrepo4/fcrepo4/pull/1499
- Issues that are ready to be worked:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2976
- Ready for review
- <your issue here>
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 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 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
- Announcements
Nothing in particular - 5.0.2
Off to the races! Yinlin has taken role of release manager. - Ecosystem release/development policy review
Yinlin had asked about the fcrepo4/docker project in the context of policies on merging PRs. There’s no official policy on the labs repositories unlike the extensions or main repositories. This is justifiable since there’s no guarantee of support for labs repositories’ code. But naturally, people can/should request reviews of PRs as a best practice. - Status on current tools
fcrepo-camel and fcrepo-camel-toolbox: the latter has some commits to master intended for release 4.7.3 that Peter’s using locally. He asks what the RC policy should be there. Daniel recommends an evaluation period for the toolbox since it is widely used. A maintenance branch should be created, an RC tag cut, and a RC announcement should be made, but there’s no need for a wiki page, etc.
Jared suggests that the maintenance branch may be superfluous as there are unlikely to be additional PRs in the interim. The evaluation period will be 1 week.
There’s a problem building both camel and camel-toolbox with how they reference the parent pom. - Next steps for import/export 4->5 migration
Daniel’s feeling is that we’re not far away from being able to do this migration. Two parallel tacks can be pursued. We can focus on round-tripping 5.x data (exporting version, exporting webacs, and importing versions). Also, create a new tool that would transform a 4.7 export to a 5 export.
It seems reasonable that we’ll make people upgrade to an appropriate version of 4.x before attempting the migration to 5.
Consensus is that this approach is sound. Documentation will indicate the versions for the export and the import, and wiring in a migration tool at that point will be straightforward.
Aaron points out that migrating the webacs could be the tricky part, since if there are containment relations between them, these will need to go away, and if there are out-links from any resources to the webacs that are not of the “this is my webac” variety, these will need to be eliminated. - 5.1.0
Item a.6 is of questionable value as it’s for a rather customized case – it’ failing tests, but if the PR authors can fix that, it will all be good.
Actions
- Danny Bernstein dig in on camel toolbox friday to see what happens if runs Aaron's fcrepo-camel changes through it
- Peter Eichman is planning to work on documenting UMD's fixity check system on the Fedora in Production: Case Studies wiki page.
- Bethany Seeger will take a look at https://github.com/fcrepo/Fedora-API-Test-Suite/issues/319
- Danny Bernstein to create a PR on master and 4.7-maintenance for the jackson-bind security update.
- Aaron Birkland to create a JIRA around the problems update the parent past 4.7
- Jared Whiklo to look into migrating from c3p0 to commons-dbcp in preparation for 5.0.2
...