[jira] [Commented] (DERBY-6996) New Java LTS phenomenon and Derby

["Rick Hillegas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451467#comment-16451467 ] 

Rick Hillegas commented on DERBY-6996:
--------------------------------------

What generally drives us to abandon old JVMs is a contributor's need to implement some fix or feature using a Java language feature which is not available in old versions. Examples of this are new versions of the JDBC spec which force new classes into the API. I haven't studied the improvements introduced by Java 10 and 11 so I couldn't say whether there is a pressing need for Derby to abandon Java 9 later next year. The current policy, agreed by the committers, is to abandon support for Java 8 starting with the next feature release (10.15.1).

> New Java LTS phenomenon and Derby
> ---------------------------------
>
>                 Key: DERBY-6996
>                 URL: https://issues.apache.org/jira/browse/DERBY-6996
>             Project: Derby
>          Issue Type: Improvement
>            Reporter: sagar
>            Priority: Major
>
> Java will now have a 6 monthly release cycle and an LTS every 3 years.
> So the next LTS is Java 11 to be released in September 2018.
> Will Derby also have LTS.
> I propose that Derby supports only LTS releases of Java.
> As in Derby 11 would be Java 11 LTS.
> Then 3 years later a major release of Derby to coincide with Java LTS.
> In between there could be point releases for fixing bugs or incorporating absolutely non ignorable performance enhancement in the 6 month Java release.
> Just a suggestion.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)