Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

Attendees

Agenda

  1. 4.7.5 release testing - discussion of where things stand
  2. Sign up for API Alignment sprints by adding your name
  3. Delta Document,  Sprint Optimization, and due dates
  4. Compatibility Test Suite 
  5. Pairtree/Appletree options
    1. Proposal (based on group discussion)

    2. As yet undecided
      1. when pair tree node creation is enabled should performing a GET or HEAD
        1. return non-pair tree children as they do now?
        2. return a 400 series message (404 or 405)?
      2. If both 1 and 2, what should the default behavior be? 
  6.  - Also move forward with creation-side resolution?
  7. External Content: Redirect or Proxy? on fedora-tech
    1. (TBD only is appropriate people are on the line)
  8. Java release schedule and compatibility planning
    1. See http://blog.joda.org/2018/02/java-9-has-six-weeks-to-live.html
      1. "With a release every six months, it is important to decide on an approach to the release train."

Ticket Summaries

  1. Please squash a bug!


  2. Tickets resolved this week:


  3. Tickets created this week:


Minutes

4.7.5 Release

  1. Kevin Ford's issue has been resolved - was due to hardcoded config in the release artifact
  2. Solr issues have been observed in testing

API Alignment Sprints

  1. Please sign-up

Pairtree/Appletree going forward

  1. Proposal:
    1. by default, minted identifiers should not have any pairtree structure
    2. by supplying a system property, the current pairtree generation can be restored
    3. retrieving the pairtree nodes should either a) require a second system property or b) not be supported at all
  2. Peter Eichman is working on a document specifying behavior of container segmentation
  3. There is concern about support for the "pairtree workaround" going into 5.0.0