Page History

...

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

1. 4.7.5 Release
   1. Danny Bernstein had a question regarding 4.7.5 RC branch push to 4.7.5 maintenance.  Have to open a PR from release branch to maintenance branch.   As it's no longer an RC, we don't need that in the name.  So 4.7.5_RC pushed to → 4.7.5 release pushed to → 4.7 maintenance.  

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

   1. Bethany Seeger created PR this am. No remaining questions. 
3. Updates from spec editors on External Content: Redirect or Proxy?
   1. no spec editors here, so tabled til next week. 
4. Compatibility Test Suite 
   1. Looked at  LDP Test Suite Report.pdf
   2. Some of the things failing here are MAY or SHOULD, so does that count as a failure?  
   3. Throwing of a 409 - is acceptable and expected in some case, but shows up as a 'fail'.  The report could use another column that shows if the test is a MAY or SHOULD and whether or not a faillure is acceptable in certain cases (as in expected, in which case it wouldn't really be a failure). 
   4. Jared Whiklo to make an issue on in the test repo for this.    
5. Delta Document Progress Review
   1. First section. Jared Whiklo made a minus box for things that are not applicable.  There are cases where you must be able to distinguish between something and that sounds more like a SHOULD then a MUST. 
   2. Changing interaction model - Jared was able to add NonRDFSource to something that was an RDFSource - it worked but what does it mean?  Not clear on how to change the RDF interaction model. Ie, how to go from an RDF Container to a RDF Direct container.  Was it patch or link header?  Jared will look into this more. Danny Bernstein thinks there might be a JIRA ticket for this. 
   3. Danny Bernstein worked on the versioning part.  He noted how the memento stuff is on a separate branch so he needed to test from there.  When to merge?  Probably only after we can create mementos, so not yet.  Noted that there was a spec change in how versions are created.  Most of the things in section 4.1 were not working yet. 

Action Items

•  Danny Bernstein to look for JIRA ticket around changing interaction model type. 
•  Jared Whiklo to create issue for the pass/fail on the Compatibility Test Suite