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

Yonik Seeley commented on LUCENE-6722:
--------------------------------------

bq. As it stands now there are only 12 – twelve – changes that are Trunk-only, 
and none of those are major features (many are deprecations). Probably because 
devs (or their boss?) prioritize getting every single commit backported to 5.x 
right away.

Yep, that's where I am.  If humanly possible I want every single feature in 5x 
so users can actually use them.  Who wants to develop something for trunk only 
when you have no idea when it will actually be released?  And who want's to 
change existing code in trunk too much if it causes pain/conflicts backporting 
to 5x? Not me :-)  I purposely keep trunk and 5x as close as possible.  Given 
that, using "are there enough differences in trunk" as a release metric is 
obviously pretty flawed.
As Mark points out, a lot of activity will happen once people feel a new major 
release coming.


> Java 8 as the minimum supported JVM version for branch_5x
> ---------------------------------------------------------
>
>                 Key: LUCENE-6722
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6722
>             Project: Lucene - Core
>          Issue Type: Wish
>            Reporter: Shalin Shekhar Mangar
>            Priority: Blocker
>             Fix For: 5.4
>
>
> Require Java 8 as the minimum supported JVM version for branch_5x.
> # Java 7 is already EOL'ed
> # Trunk is already at Java8
> # Important Solr components such as Jetty 9.3.x already require Java 8
> # Nashorn Javascript engine available in Java 8 is just so much faster and we 
> may see more usage of JS inside Solr (SOLR-7576 etc.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to