...

1. Announcements
   1.  6.0.0 Beta Release
2. Plan for Beta
   1. Target release date for 6.0.0
   2. Development
      
      1. core
      2. external utilities
      3. ?
   3. Testing
      1. Migrations
      2. Scalability/Performance : Performance Testing Criteria
      3. ?
3. Life after 6.0.0
4. Pilot Update
5. PRs needing attention
6. New Issues: 

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

7. <Your topic here>Camel and Solr

Tickets

1. In Review

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

2. 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

   
   

3. 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

   
   

4. 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

   
   

Notes

1. Announcements
   1. David says that there's a lot of interest in Fedora 6.
   2. UC Davis is interested in F6
   3. Mike Ritter will be joining next week
2. Sprint
   
   1. Review of the Board
      1. documentation review remaining
      2. solr and camel integration will be pushed back in later sprint 
      3. rebuild speed issue Danny added in fix in code and merged
   2. Sprint going well
   3. What is the target for the final release? What tickets still need fixed? Where is the line?
      1. release planned for Monday next week
      2. Jira ticket 3640 review timestamp issue remaining, not a beta release blocker
3. Questions/discussions: 
   1. is fcr:fixity still considered deprecated?
      1. There are some users who expect this functionality to exist
      2. Leave it till there's a viable replacement
      3. Something needs to be added to the spec
   2. Do we need F2 code in the migration utils?
      1. Unsure if the F2 code works or if anyone still uses F2
      2. Seems like it's okay to remove
      3. Ben wants to migrate the entire FOXML without splitting it up as part of a PLAIN_OCFL migration
         1. Ben will add PR to the feature
   3. Removing fcrepo-config.xml
      1. https://github.com/pwinckles/fcrepo4/commit/16205c9e0386048e5138c2cd402d55066170ed23
      2. Moving beans to Java Config and adding properties for configuring without touching spring
      3. Should be fine for most use cases. Unclear if people have custom auth configurations that may be more difficult for them to configure – still requires custom spring config
4. Performance Testing
   
   1. Performance Testing Criteria
5. PRs
6. 1. The last sprint was very successful and Beta has arrived.  The future is now.
   2. Upcoming user group meetings for Europe in March and North America in April.
7. Post-Beta Plans
   1. Shooting for April to Release 6.0.0
   2. What to do other than obvious bug-fixes and community feedback?
      1. Test databases other than postgresql, specifically MySQL, esp 5.7
         1. Issue with 503 character limit for IDs is looming. Will need to reach out to see if it would affect anybody.
      2. Updating the camel-toolkit
         1. Drop OSGi and make spring boot jars
         2. Do we offer these seperately or make one box that you can configure to run only the services you need
         3. We'll set up a meeting to go over the strategy for moving off of Karaf and how best to provide that to the user
   Your topic
   1. Ben C wants an switch build into migration util that does OCFL java validate datastream checksum compute that will be migrated comparing and validate with what is in foxml in fedora 3

Actions