Page History

...

1. Sprint Update
   
   1. Board
   2. Backlog
   3. WebACL
   4. Versioning
   5. Compatibility Test Suite
2. Post Sprint Planning
   1. Who can commit to landing 5.0.0 for release
      1. Loose ends
         1. Completing the API alignment tasks
         2. Documentation 
            1. Adopters Guide
            2. FEDORA5x Review 
         3. Bug fixes

3. Messaging headers: should they stay or should they go? who is using them? Camel? 

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

   : 

   1. Are we comfortable with messages emitted?Shall we consider using Duraspace checkstyle rules?

5. Checkstyle Analysis

   1. Repo
   2. There are three rules in the fedora checkstyle rules that are not in the Duraspace checkstyle rules: 
      
      1. requiring @author in javadoc
      2. "final" required for parameter variables
      3. "final" required for local variables
6. Mailing list: Kevin Ford's inbound links question

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

   
   

...