Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Audio/Video Conference Link: https://lyrasis.zoom.us/j/396037251
  
  • Meeting ID: 396 037 251
  • Find your local number: https://lyrasis.zoom.us/u/ad6Xb7q3ia

  • Join fedora-project.slack.com on the "tech" channel

  • Self-register at: http://slack.fcrepo.org/

Attendees 

1. Danny Bernstein
2. David Wilcox 
3. Jared Whiklo  
4. Peter Winckles 
5. Daniel Lamb 
6. Ben Pennell 
7. Thomas Bernhart 
8. Calvin Xu 
9. Michael Ritter 

Agenda

1. Announcements
   1. Jira has been moved: https://fedora-repository.atlassian.net/secure/RapidBoard.jspa?rapidView=3
   2. Camel toolbox sprint is on hold
2. 5.1.x release
3. 6.0.0 Release Schedule
   1. RC
   2. Production
4. Updates on the performance improvement work
   1. Short-lived transactions related issues
      1. https://fedora-repository.atlassian.net/browse/FCREPO-3695
      2. https://fedora-repository.atlassian.net/browse/FCREPO-3697
      3. https://fedora-repository.atlassian.net/browse/FCREPO-3696
   2. Migration Utils slow-down
      1. Status of instrumenting migration-utils with micrometer: https://fedora-repository.atlassian.net/browse/FCREPO-3692 
         
         
5. Pre release short list of bug fixes and improvements
   
   1. https://fedora-repository.atlassian.net/browse/FCREPO-3620
   2. https://fedora-repository.atlassian.net/browse/FCREPO-3561
   3. https://fedora-repository.atlassian.net/browse/FCREPO-3638
   4. https://fedora-repository.atlassian.net/browse/FCREPO-3672
   5. https://fedora-repository.atlassian.net/browse/FCREPO-3690
   6. https://fedora-repository.atlassian.net/browse/FCREPO-3691
6. Any other new tickets/issues to be considered for the release
7. Your topic

Tickets

1. In Review

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

2. Please squash a bug!

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

3. Tickets resolved this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

4. Tickets created this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes

Actions

• Look through migration util commits since December to see if there are any potential causes of performance drop off.