...

• A. Soroka
• Jared Whiklo 
• Danny Bernstein 
• Esmé Cowles
• Katherine Lynch
• Marcus Barnes
• Nat Kanthan
• Daniel Lamb
• Michael Durbin
• Jim Coble
• Yinlin Chen
• Youn Noh
• Bethany Seeger
• David Wilcox
• Frank Smutniak
  
• Unknown User (acoburn)
• Jonathan Green
  Joe Harrington
• 
  

Agenda

1. 4.7.0 release candidate - testing and migration
   
   1. Backup/Restore issues
2. 4.6.1 release - patch for concurrent resource creation
3. Semantic versioning, API Specifications and releases post-4.7.0
4. new fcrepo-vocabulary repository?
5. API Specification - Taking it to the streets
6. Move Yinlin's tests into fcrepo4-labs...

7. Status of "in-flight" tickets

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

...

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

Status of release testing:

1. The process seems to be going well.
   1. ActiveFedora issue does not seem to be a blocker.  Ideally Drew can provide feedback before we turn the crank.
   •  Danny Bernstein will rerun steps that seemed to be broken.
2. Release schedule: Halloween? Let's plan for early-ish on Monday after talking to Drew and Stephano.

• •  Jared Whiklo is concerned that we haven't  the data migration enough - will touch base with Drew
  •  Andrew Woods will circle up with Stephano and the gang about migration
  •  Andrew Woods will check with Drew that all is well with   Michael Durbin's 4.6.1 patch  before dropping the monkey.
    
    

Semantic versioning, API Specifications and releases post-4.7.0

The community wants semantic versioning.  

But the community wants no more than one major release per year,  minor releases as necessary.

There are two factors that define a major release:

1. breaking changes to the API
2. required backend data migration

Ideally we would finish the API work before the next major release (5.x). 

Should we strive for this?   Yes:  there is a consensus on the call.

Do we think that we'll need more near term releases with breaking changes at the REST API level before we get to 5.x? 

Is 6-8 months enough time to solidify the REST API and align the implementation with it? 

• A robust test suite should be part of that alignment.