On 9/14/2014 10:32 AM, Anshum Gupta wrote: > I don't have a really strong opinion on 'Should we move to Java 8' but > at the same time would not really be happy dealing with 2 continuously > diverging branches. I wouldn't want to rewrite the same implementation > twice over and get it to work. > > I am not sure about others but I think it will also make it tougher to > attract contributors knowing they might have to deal with 2 divergent > branches. > > At the same time, if there's a reason compelling enough that makes the > lives of everyone involved better (read, easier), I'll be in for it.
My vote remains +0. I don't think we're ready quite yet, but I'm not going to be horrendously upset by the move if it happens. I might get really annoyed with complications in backporting, but I'll work through those problems. If anyone cares, my advice is to wait until just before branch_5x is created to require Java 8. Anshum managed to fully articulate what I was trying to say in my message earlier. I absolutely think we do need to make a move to Java 8 as the minimum on trunk, and it likely needs to happen soon. When we do it, we need to be ready to ignore whatever outcry there is from the userbase about how they cannot upgrade Java on their production systems. There will be 4.x versions for those users. They're going to get left in the dust feature-wise, but this is what happens as software projects evolve. I would expect this to not be new information for many of you: I'm in this for Solr. Solr is inherently dependent on Lucene, so I care very much about Lucene, but my focus is Solr. My understanding of Lucene (even the Lucene usage in Solr) is limited. One of our stated goals for Solr 5.0 is to make it a standalone app, possibly with a controlling process. This goal, and the removal of the war target in trunk, mean that Solr 5.0 is not ready for release in its current form. The effort required to build a standalone app looks pretty daunting, although it's possible that embedding Jetty might be really easy. Depending on what we learn regarding converting a servlet to an app, we might need to reinstate the war target in order to make a reasonably quick Solr 5.0 release possible. If that happens, we can migrate to a standalone app in a branch off the new trunk and backport the new build target into branch_5x. Completely switching to a standalone app and eliminating the servlet might need to wait until 6.0 ... and it would be good motivation for 6.0 to follow 5.0 relatively quickly. Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
