Page History

...

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

   
   

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