Versions Compared

Key

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

...

Attendees 

...

Attendees

Agenda

  1. 4.7.5 release - Planning for week of January, 15th 2018
  2. Fedora 5.0.0
    1. Release date target
    2. PairTrees / AppleTrees
  3. Tickets requiring attention
    1. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-2520
      - Bethany Seeger
      1. Any more discussion needed here?  If a mimetype goes in, it should come out at the very least. 
      2. Bethany Seeger suggested an alternative implementation: https://github.com/fcrepo4/fcrepo4/pull/1272#issuecomment-353173508 that would move the check closer to the HTTP layer
      3. Ralf Claussnitzer: Sounds reasonable. HTTP servers should respond with BAD REQUEST if given an unparsable mime type string.  Should the repository layer check again?

    2. Expand
      titleIn Review...

      Jira
      serverDuraSpace JIRA
      jqlQueryfilter=13100
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  4. ...

...

  • Memento
    • Jared - would like more people to look at this.
    • Danny DannyB will be helping review this and get it over the hump
  • Webac is fairly close.
  • Page with all the test results from comparison: https://wiki.duraspace.org/display/FEDORAAPI/Fedora+API+Spec+and+Delta+Document+Verification
  • Compatibility test suite - which is intended to be completed around April. Roughly a bit over halfway done, but needs to be verified.
  • CRUD operations are pretty close, just a few things remaining

Looking for point people to verify alignment

  • Memento - Jared and DannyDannyB
  • CRUD - Jared
  • Webac - Aaron AaronB and Peter(?). There are testing scripts, including Authz tests.
  • Fixity - Bethany
  • Messaging - AaronAaronB

Sprints?

Approach was to see how far we got before the holidays. Not a lot got done in the meantime.
Andrew: at a minimum, set up at least one sprint to finalize things
   Would another earlier sprint be useful?
Jared: just pick a time, can probably get time allocated. It is an effective way to clean up small chunks of work, get testing done
Peter suggesting a february/march sprint is a possibility
Most people would prefer a sprint versus doing adhoc work
Aaron: With a date for a sprint he can at least ask.
Andrew: inclination is to do two sprints:

...

Bethany: Aaron C. mentioned blank nodes don't work well with Apple Trees, would want to check to make sure this is compatible
Andrew: Copy and move operations will not work with Apple Trees. Messages as they are currently emitted would not suppress the pair tree structure
Bethany: When 5.0 is put out there are ripple effects for the camel-toolbox since the messaging will have changed.
Aaron B: Does the apple/pair tree question have relevance to the import/export machinary that people might use to go from 4 to 5?
It sounds like we have one scenario where if we don't have pair trees in fcrepo5, would the intermediate nodes be 404s?
Is there a scenario where pair tree uris might be illegal in fcrepo5?
Esme: Thinks they would migrate over, but creating new uris might be different.  Definitely are questions about how behavior would need to be different in fcrepo5 when migrating from 4.
Aaron: Along those lines, what about someone migrating from fcrepo4 to a different fedora impl?
Andrew: import/export tool should help with that sort of migration. Decision of 5.0 should be independent.
Aaron: impls without concepts of pair trees could be an issue.
Esme will put together that wiki page to contain the discussion

3. Tickets requiring attention:

...