Page History

...

1. Upcoming Sprints
   
   1. Please sign up
   2. Focus of each sprintSprint 1: Release 5.0
      1. Optimally we start Sprint 1 with a release candidate  
      2. Complete documentation
      3. Wrap up the compatibility test kit
   3. Sprint 2: Ecosystem Tools
      1. Camel Toolbox
      2. Java Client
      3. Import/Export
   4. What is the best way to prepare as a team?
2. On the subject of Import/Export...
3. Getting to 5.0 Release Candidate
   1. In progress tickets
      

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

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

   2. Remaining external content (low-hanging: ie volunteers?) issues:

      Expand
      Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery key in (FCREPO-2776,FCREPO-2801,FCREPO-2752,FCREPO-2802,FCREPO-2796,FCREPO-2797) serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

   3. 5.x Documentation Effort matrix
4. Sidecar specification update
   1. Review Spec committee's direction on Fedora API Specification github issue (one-step fixity check)
      
      1. Also what about dangling question about storing checksums as a server managed triple? 
      2. Fedora API Specification "Candidate Recommendation #2" in the process of being released
      3. Fixity check encouraged as a sidecar specification
   2. Transactions
5. <Add your agenda item here>

...