...
- Danny Bernstein
- Aaron Birkland
- Bethany Seeger
- Ben Pennell
- James Silas Creel
- Jared Whiklo
- Jon Roby
- Peter Eichman
Agenda
Announcements
- Unanswered mailing list messages
- Status of ecosystem tools:
- Java Client Release
- fcrepo-camel
- camel toolbox
- 5.0.1 Release Notes
- 5.0.2:
- issues
- Ready for review
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO- 2977 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO- 2975 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2978
Call for release manager
- Date?
CTS appears to have three new failures : https://github.com/fcrepo/Fedora-API-Test-Suite/issues/319
- Unanswered mailing list messages
- Status of ecosystem tools:
- Java Client Release
- fcrepo-camel
- camel toolbox
Next steps for import/export/4→5 migration
- Initial investigation
- Volunteers for a task force
- 5.1.0
- Ready for review1889
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-29751889 - "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-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 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2976
- Ready for review1889
- <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
Actions
- Announcements
- fcrepo-java-client released and ready for use
- 5.0.2
- The two bug fix tickets should now be merged in
- There is still a lingering issue with C3P0
- We could try to remove it, or wait for a fix on their end in the next few weeks.
- The maintainer has indicated they will probably resolve it in the next week or so
- Fcrepo-2977 is a fairly significant issue, dbernstein suggests not waiting more than a few weeks
- whikloj: commons-dbcp may be a potential replacement http://commons.apache.org/proper/commons-dbcp/
- Looking for someone to do release of 4.7.5
- CTS new messages
- 2977 and 2975 were both merged. 2977 was tested against the CTS, 2975 was not
- Could be a timing issue, or the number of messages. It was expecting 2 messages, there might be 3 now because of the immediate creation of timemap
- Bethany: isn't this a fedora-ism? Would other implementations pass? Maybe it should just test for at least one message.
- Would be good to know how many messages are being received
- Don't want to change the test to match the community implementation, needs to work for all impls.
- Need to determine what the issue is first
- Do we need to get messages for creation of timemaps?
- Ben: for indexing purposes this is helpful
- Whikloj: should we be able to provide the number of expected messages by implementation?
- Bethany: maybe do this later, in short term could do the more minimal route
- Bethany: happy to take a look to confirm that the issue is the number of messages
- 2977 and 2975 were both merged. 2977 was tested against the CTS, 2975 was not
- Mailing list question - reindexing
- Peter was going to follow up, ask how they are triggering the reindexing service
- Ecosystem tools
- fcrepo-java-client - completed
- camel
- Peter wants to take a look at Aaron Birkland's camel work, but has gotten bogged down
- dbernstein: would it be useful to gather a team for this?
- Peter: Could be useful to have a mini-sprint to devote to it. Is guessing its not huge, but larger than we suspect it is
- AaronB: There are processors that create headers, so the amount of work that depends on the headers vs the body
- If it just looks at headers, might not be much work. If looks at body, that'll be more work.
- Guessing translating the headers is most of the work
- camel toolbox has its own integration tests, which should be helpful for testing it
- need to get fedora setup for these tests
- Need to get PR for updates to fcrepo-camel merged before we will be able to do testing of the toolbox
- Peter will talk to his supervisor next week about carving out a week to devote to this
- Danny will dig in tomorrow to see what happens if runs Aaron's changes through
- Import/export
- may need to gather a group to look at the scope of the issues.
- Danny doing a bit of testing to see where things stood
- Versioning
- Import of versions is not present for 4.x
- Do we need to support this? No one has clammored for it
- There is an existing PR to add this feature, but likely wouldn't agree with
- Export and import of versions does not currently work for 5.x
- Migration from 4.x to 5.x is higher priority than 4 to 4
- Import of versions is not present for 4.x
- The changes do not seem that big, a small task force might be able to get that done
- Bethany and Peter interested in working on it, but have very limited time at the moment
- Danny would have time, but needs funding
- Ben P would need to talk to supervisor about it
- Danny will call out to community for support
- 5.1.0
- Danny is guessing 3-4 months out
- Close some of the gaps on the CTS tests that are not passing, particular the MUSTs around containers
- There are issues available to be worked
- its possible 2976 (state tokens) may need to be broken into smaller tasks
- There are a number of actions, like GET and PUT that need to be handled, as well as multiple cases
- its possible 2976 (state tokens) may need to be broken into smaller tasks
- Ben: Where will https://github.com/fcrepo4/fcrepo4/pull/1501 be included? 5.1.0 or 5.0.x?
- It is going to go into 5.1.0
- Checking in with Peter about UMD fixity checks being stored in fedora
- Peter going to add use case results somewhere in fedora documentation. Is there a place for this kind of thing?
- Danny will find a spot for it and pass along a link
Actions
- Peter Eichman will talk to his supervisor next week about carving out a week to devote to fcrepo camel toolbox
- 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
- Peter Eichman will respond to mailing list question: [REINDEXING SERVICE] Question about how it works
- Checking with Peter Eichmanregarding: UMD is storing checks and results for fixity checks inside Fedora, it would be good to capture this process in the community documentation.
- Danny Bernstein will reach out to Yinlin Chen to see about a fcrepo4-docker release with the 5.0 architecture.
...