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
- IRC:
Attendees
Agenda
- 4.7.5 release testing - discussion of where things stand
- Sign up for API Alignment sprints by adding your name
- Delta Document, Sprint Optimization, and due dates
- Compatibility Test Suite
- Pairtree/Appletree options
Proposal (based on group discussion)
As yet undecided
when pair tree node creation is enabled should performing a GET or HEAD
return non-pair tree children as they do now?
return a 400 series message (404 or 405)?
If both 1 and 2, what should the default behavior be?
- Also move forward with creation-side resolution?
- External Content: Redirect or Proxy? on fedora-tech
- (TBD only is appropriate people are on the line)
- ...
Ticket Summaries
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
4.7.5 Release
- Kevin Ford's issue has been resolved - was due to hardcoded config in the release artifact
- Solr issues have been observed in testing
- Solr config is set to use autosoftcommit: 1000ms
- Some custom predicates do not get indexed
- Likely all is well
API Alignment Sprints
- Please sign-up
Pairtree/Appletree going forward
- Proposal:
- by default, minted identifiers should not have any pairtree structure
- by supplying a system property, the current pairtree generation can be restored
- retrieving the pairtree nodes should either a) require a second system property or b) not be supported at all
- Peter Eichman is working on a document specifying behavior of container segmentation
- There is concern about support for the "pairtree workaround" going into 5.0.0