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 

• Danny Bernstein 
• Esmé Cowles 
• Aaron Birkland
• Jared Whiklo
• Bethany Seeger
  
  

Agenda

1. What are details that we should articulate related to a proposed 4.7 LTS?

2. Gradle as build tooling
3. Possible messaging memory leak?  
4. Tickets/PRs that need merging:
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - PR#1213 (4.7-maintenance cherry-pick)
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - PR#1220 (4.7-maintenance cherry-pick)
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - PR#45 (4.7-maintenance cherry-pick)
5. Ben Pennell's Import Export of Versions PR https://github.com/fcrepo4-labs/fcrepo-import-export/pull/109

6. Status of "in-flight" tickets

   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.

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

1. Intent and ground rules for LTS:
   1. How long will the LTS be maintained?  When do we stop supporting it? 
      1. Consensus: 3 years
         1. Jared Whiklo:  smaller institiutions need reassurance that investments in technology will have some known duration.
            
            1. There are still people using Fedora 3.7.x
      2. Esme proposed an annual review of who is using it and semi-annua/annual commitments to maintain the LTS
         1. Jared Whiklo:  won't instill confidence in smaller institutitions if a version can go away when committers decide we are no longer interested in maintaining.
         2. Esmé Cowles :  yes,  making explicit the general timescale for maintainence is important in any case.
   2. What will be maintained? 
      1. Bug fixes
      2. Migration paths to later versions?
      3. No commitment to backporting features
      4. ongoing JVM support?  
         1. Doesn't sound like fun, but java 8 is approaching end of life. 
         2. To be evaluated in the annual review:  Question depends of whether users have options.
         3. Perhaps we should not necessarily commit to support Java 9.   But will support it to the extent that there is community interest.
      5. ?