Time/Place

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

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Dial-in Number: (712) 775-7035
  • Participant Code: 479307#
  • International numbers: Conference Call Information
  • Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
• IRC:
  
  • Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #fcrepo on irc.freenode.net

Attendees 

• A. Soroka
• Jared Whiklo 
• Bethany Seeger
• Yinlin Chen 
• Benjamin Armintor
• Andrew Woods
• Allen Flynn 
• Namita Bahulekar
• Longshou Situ
• Esmé Cowles
• Unknown User (acoburn)

Agenda

1. 4.5.1 RC-3 testing status - and release plans, this Friday!

2. Release candidate policy - feedback on wording?
3. F4/Modeshape5 
   1. PR status:
      1. Good
         1. Mode5 PR works
         2. Config: File works
         3. Config: MySQL works

         4. Removed default fcrepo.modeshape.configuration

      2. Bad - not so bad

         1. Config: PostgreSQL not working - but likely easy

         2. Config: Clustering - untested, but should be able to work

            1. Binaries are copied across instances
            2. Use central object db

         3. Config: Servlet-auth, has not worked in years

         4. Bug in Mode: https://github.com/ModeShape/modeshape/commit/bc574455aa7e0e7fa6f7a6e4820f5b777bfda3f1#diff-0bfcd93b5cc4efa01e1328b6fcb4c8c4L1987

         5. Federation not refreshing when new files added

   2. Migration testing volunteers needed
4. Review Versioning Spec - meeting @2pm ET, Tues May 3rd
5. Thoughts on multi-tenancy
6. ...

7. Status of "in-flight" tickets

   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.

Ticket Summaries

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

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

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

Minutes