Page History

...

1. Volunteers for running the weekly meeting: 
   
   1. 5/17:  Bethany Seeger
   2. 5/24: Jared Whiklo? 
   3. 6/7: Cancelled
2. Feedback on /fcr:fixity  endpoint
3. Getting to 5.0 
   
   1. Review of work that happened this week: 
      1. 6 PRs merged
      2. Documentation:  Kevin Ford has kicked it off. 
      3. External content (proxy, copy, and redirect) 
   2. 5.x Documentation Effort
      
      1. 5.x Documentation Updates matrix
   3. Another sprint? 
      1. Timeframe/Duration/Availability
   4. Ecosystem tools dependent on the release:
      1. import export tool
      2. camel tool kit  
      3. fcrepo4-vagrant
      4. java client 
      5. api-x 

4. Jira
   server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2604

   : 
   

   1. Are we comfortable with messages emitted?

5. ?

Ticket Summaries

1. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

2. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

3. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

Minutes

Facilitating upcoming meetings

1. 5/17: Bethany
2. 5/24: Jared? - Danny to reach out
3. 6/7: cancelled

Feedback on /fcr:fixity endpoint

1. Deprecate in 5.0
2. Community has indicated interest in retaining the feature for now

Getting to a 5.0 release

1. Great progress this week

External Content PR is in good shape for merge

1. All flavors supported: redirect, proxy, copy
2. One outstanding issue: one test is being @Ignored
   • ACTION: Bethany to capture in a new ticket

Documentation

1. Kevin Ford has been making good progress
2. Adding sign-off of 5.0 wiki documentation to release process
3. Yinlin interested in helping with documentation
4. ACTION: Danny to update documentation table to align states with JIRA states
   • https://wiki.duraspace.org/display/FF/5.x+Documentation+Updates

Sprint schedule

1. Sprint A - summer
   • Feature completion
   • Documentation
   • Compatibility Test Suite, contract work?
     • We should create granular CTS tickets
     • Valuable having "third-party" interprete spec and create unbiased tests
   • Testing
2. Sprint B - sept
   • Bug resolution
   • Critical backlog tickets?
   • Ecosystem tools
     1. import/export
     2. camel-toolbox
     3. vagrant
     4. java-client
     5. api-x
3. What is the target release date?
   1. Ideally 2018... mid-Oct
   2. ACTION: Danny to create a sprint date doodle
   3. Need to avoid scope-creep
   4. Identify other features that we would like sooner than later

Actions

•  Danny Bernstein Create a ticket to check whether or not the fcrepo-camel-toolbox still works with 5.0.  Part of that ticket is to evaluate whether or not there are dependencies on the jms.* headers included in the messages generated by Fedora
•  Bethany Seeger Create tickets to test versioning and redirect/proxy.
•  Kevin Ford Ask community about /fcr:fixity endpoint.
•  Danny Bernstein Inquire with leadership group (and broader community?) about prioritizing ecosystem tools for alignment with 5.0.
•  Bethany Seeger to create JIRA for @Ignored test in External Content PR
•  Danny Bernstein to update documentation table to align states with JIRA states
•  Danny Bernstein to create Sprint Doodle for immediate distribution