Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. 4.7.5 Release
    1. bringing it over the finish line:
      1. https://docs.google.com/spreadsheets/d/1I_zTMxh2l2rf2wpafoTwhSTR5GZuEoaTcZmTKCI3xT4/edit#gid=1769378986
  2. Sign up for API Alignment sprints by adding your name
  3. Delta Document Progress Review
  4. Compatibility Test Suite 
  5. Jira
    serverDuraSpace JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-2520
    1. Any remaining questions?
  6. Updates from spec editors on External Content: Redirect or Proxy?

Ticket Summaries

  1. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  2. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Tickets created this week:

    Expand
    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


Action Items

Minutes

...

  1. 1-2 tests for Danny Bernstein to complete
  2. Esme: will do RC-2 testing with ActiveFedora/Hyrax, or find someone to delegate to
  3. Andrew Woods: contacted Carrick Rogers about testing on their custom fedora with RC-2
  4. release is slated for next week (Feb 12)

...

  1. make it a goal to fill out each section by next week's call
  2. identify items that are out of alignment
    1. Peter: authz
    2. Danny will ping Aaron Birkland about nofitications
    3. Danny: versioning
    4. Jared & Yinlin: resource management
  3. keep in mind the spec may have been updated; make sure section numbers match up

...

  1. try running the compatibility suite
  2. add git issues as feedback
  3. code review would be extra helpful
  4. mainly covers section 3 (resource management)
  5. cross-check test suite report to manual test results
  6. "trust but verify"
  7. Yinlin: Python vs. Java test suite?
  8. Andrew: we will focus on the Java version as the official test suite

...

  1. remaining question: what is the behavior of the pairtree nodes?
  2. Esme: we need to support the current behavior
  3. Aaron Birkland feels strongly that pairtree nodes should not resolve
  4. Andrew: concerned about complexity of code and introducing bugs
  5. Bethany: could we only have 1 setting?
  6. Andrew: need to support migration of existing pairtrees, so generation needs to be separate from retrieval
  7. Esme: minting behavior is easy and tidy; UUID-only minter should be very easy to write

...

  1. Bethany: putting in a check of object values in PUT/PATCH requests that mime types are syntactically correct
  2. ebucore:hasMimeType is treated as a special case since it is used as the content-type of a binary resource on GET

...

  1. Peter, Esme, Doran agree
  2. Peter: start from the draft Prefer header spec that Ben Pennell created
  3. Doran: NLM has a particular interest of this
  4. Doran: there could be interplay between this and the Oxford Common File Layout
  5. Andrew: need to make sure we capture real uses cases

...

  1. many repos set up once and then not update to maintain stability as long as they can
  2. desire for compatibility with new versions of Java
  3. new language features that implementors might want to use

...