Time/Place
This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
- IRC:
- Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #fcrepo on irc.freenode.net
Attendees
- Danny Bernstein
- Esmé Cowles
- Aaron Birkland (will be late)
- Jared Whiklo
- Bethany Seeger
- Christopher Johnson
- Joshua Westgard
- Michael Durbin
- David Wilcox
- Yinlin Chen
- Peter Eichman
- Carrick Rogers
- Ben Pennell
Agenda
Upcoming "Alignment to Spec" sprint
- Progress on: Possible messaging memory leak?
- Need volunteer for:
- Solution is outlined in ticket
- LTS policy proposal
- Wrapping up fcrepo-import-export-verify: https://github.com/fcrepo4-labs/fcrepo-import-export-verify/pull/48
- Report on 4.7.4 Benchmarks and Testing (Carrick Rogers)
- Future of PairTrees and https://github.com/fcrepo4/fcrepo4/pull/1223
Status of "in-flight" tickets
Ticket Summaries
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
- Avalon R6 4.7.4 Testing
Minutes
Action Items
- Esmé Cowles sanity-test backport of user-supplied namespace fix
- Aaron Birkland will update the version number of the core codebase and related modules to 5.0.0-SNAPSHOT
- Joshua Westgard will resolve agenda item 7 (https://github.com/fcrepo4-labs/fcrepo-import-export-verify/pull/48)
- Sprint starting next week -
- Danny Bernstein will not be available for the first day of sprint next week
- Update on memory leak issue from Peter Eichman
- modeshape bug - fixed in modeshape 5.4 been unable reliably get system to fail and hang in test case.
- With avoiding transaction rollbacks they were able to run the remainder of the load and it completed successfully.
- tested with batch loader? Not gotten back to that yet
- ran into another issue which may or may not be related - there were some binaries where the metadata was there, but the binaries themselves were not in the system.
- binaries were probably large enough to not hit the 4k minimum size (repository.json config)
- related to modeshape upgrade? no, this was happening in the modeshape 5.3 system causing the failed transactions he was seeing