OK, it looks like Java 7 starting with Solr 4.8 is going to happen.
May I suggest we announce this sooner rather than later? Perhaps
starting with an announcement on the user's list Real Soon Now? Like
before we break people's builds that rely on Java 1.6 with a checkin
to 4x?
There will be
Hi,
the vote is over after 72 hours. The results:
- Almost all voting committers want to move to Java 7 - only Grant Ingersoll
said -0. So I declare this as succeeded vote.
I will now proceed with committing the backports (LUCENE-5514). The Jenkins
infrastructure is already upgraded. I will
On Mar 8, 2014, at 11:17 AM, Uwe Schindler u...@thetaphi.de wrote:
[.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7 and backport all Java
7-related issues (FileChannel improvements, diamond operator,...).
-0 -- Seems a little odd that we would force an upgrade on a minor version,
which
On Tue, Mar 11, 2014 at 6:11 AM, Grant Ingersoll gsing...@apache.org wrote:
On Mar 8, 2014, at 11:17 AM, Uwe Schindler u...@thetaphi.de wrote:
[.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7 and backport all Java
7-related issues (FileChannel improvements, diamond operator,...).
-0
@Furkan,
thanks for sharing your thoughts and giving insights. I am happy that
you agree that we should move to Java 1.7 even if you had the trouble
with your legacy code. That is the right way to go here!
Regarding the vote:
+1 for moving to Java 1.7 on 4.x
-1 for moving to Java 8 on trunk I
Hi,
it looks like we all agree on the same:
+1 for Lucene 4.x requirement on Java 7.
-1 to not change trunk (keep it on Java 7,too).
I will keep this vote open until this evening, but I don't expect any other
change. Indeed, there are no real technical reasons to not move.
I was expecting the
Its too sad this decision isn't about what is best for attracting new
developers, but instead corrupted by corporate policies around JVM
versions and the like.
what a shame, open source isn't supposed to be like that.
On Mon, Mar 10, 2014 at 5:46 AM, Uwe Schindler u...@thetaphi.de wrote:
Hi,
On Mon, Mar 10, 2014 at 5:46 AM, Uwe Schindler u...@thetaphi.de wrote:
Hi,
it looks like we all agree on the same:
+1 for Lucene 4.x requirement on Java 7.
-1 to not change trunk (keep it on Java 7,too).
I will keep this vote open until this evening, but I don't expect any other
change.
+1 for 4.x on Java7
-0 for rushing trunk to 8 now
Rob, in my view, what's best for Lucene as a project is tightly linked to
what's best for its users. And the users tend do be corporate. I think users
are so important that we should even consider rolling a bugfix-release from the
4.7 branch
I tend to think Java 8 still requires a fair share of testing before
it'll make it to production... Check out this recent marvel :)
http://marc.info/?l=openjdk-compiler-devm=139410546908373w=2
On Mon, Mar 10, 2014 at 1:37 PM, Jan Høydahl jan@cominvent.com wrote:
+1 for 4.x on Java7
-0 for
On Mon, Mar 10, 2014 at 8:37 AM, Jan Høydahl jan@cominvent.com wrote:
Rob, in my view, what's best for Lucene as a project is tightly linked to
what's best for its users. And the users tend do be corporate. I think users
are so important that we should even consider rolling a
On Mon, Mar 10, 2014 at 8:44 AM, Robert Muir rcm...@gmail.com wrote:
When making votes like this, please do what you think is best for the
open source project, instead of what you think is best for your
corporation.
Also, please show respect for the opinions of others. If they happen
to
On Mon, Mar 10, 2014 at 8:49 AM, Yonik Seeley yo...@heliosearch.com wrote:
Also, please show respect for the opinions of others. If they happen
to disagree with you,
do not assume it's crap and driven by corporate interests.
No assumptions had to be made. it was explicitly worded in the
Hi Robert,
the vote must be held open for 72 hours. I haven't even had a chance to
formulate my VOTE+reasoning yet, and i dont agree with this crap here.
Indeed, there is no need to hurry! I just wanted more discussions coming in.
The merges I prepared already are stable and pass all tests,
On Mon, Mar 10, 2014 at 9:00 AM, Uwe Schindler u...@thetaphi.de wrote:
I agree with you: trunk is our development branch, I see no problem with
making it Java 8 only. From the other issue, we have no important news to
actually release this as 5.0 soon, so we can for sure play with it for long
Solr/Lucene 4.8 - Java 7
+1
I'm not too sure about moving trunk to java 8 . Let's keep it at java 7 and
make a call when we are closer to Lecene-Solr 5.0. Organizations move to
newer versions of java very slowly.
On Mon, Mar 10, 2014 at 6:30 PM, Uwe Schindler u...@thetaphi.de wrote:
Hi
I agree with you on the fact that we should always try to innovate.
Moving to Java8 is innovation and we should do it rather sooner than
later. I just don't think we should move there right before it's even
released. I can totally see this vote coming in in a couple of month
once we have fixed the
Hi Yonik,
Excuse me? I assume that's aimed at me?
No, that was not aimed at you. It was a general comment. There are many
examples of companies /users that fork trunk. Lucid Imagination was one of them
(the product LucidWorks was initially based on trunk, as far as I remember).
Also P.S.
[.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7 and backport all Java
7-related issues (FileChannel improvements, diamond operator,...).
+1
[.] Move Lucene/Solr trunk to Java 8 and allow closures in source code.
This would make some APIs much nicer. Our infrastructure mostly supports
this,
On 08 Mar 2014, at 17:17, Uwe Schindler u...@thetaphi.de wrote:
Hi all,
Java 8 will get released (hopefully, but I trust the release plan!) on March
18, 2014. Because of this, lots of developers will move to Java 8, too. This
makes maintaining 3 versions for developing Lucene 4.x not
[.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7 and backport all Java
7-related issues (FileChannel improvements, diamond operator,...).
+1 totally!
[.] Move Lucene/Solr trunk to Java 8 and allow closures in source code.
This would make some APIs much nicer. Our infrastructure mostly
2014-03-08 17:17 GMT+01:00 Uwe Schindler u...@thetaphi.de:
Hi all,
Java 8 will get released (hopefully, but I trust the release plan!) on
March 18, 2014. Because of this, lots of developers will move to Java 8,
too. This makes maintaining 3 versions for developing Lucene 4.x not easy
Solr/Lucene 4.8 - Java 7
+1
Solr/Lucene 5.0 - Java8
-1 for now. +1 as we get closer to releasing 5.0. There's still plenty
of cruft in trunk that's there only because of needing to support
Java6 in the 4.x code line, I think having a period when we can freely
clean up some of the Java 6
Hi All;
I am not a committer yet but I want share my thoughts as a contributor and
a Solr user to give an example from real life. I use SolrCloud for one year
(our product is at pre-prod step) and I have hundreds of servers at my
company and nearly half of them are SolrCloud. We also have an
Hi all,
Java 8 will get released (hopefully, but I trust the release plan!) on March
18, 2014. Because of this, lots of developers will move to Java 8, too. This
makes maintaining 3 versions for developing Lucene 4.x not easy anymore (unless
you have cool JAVA_HOME cmd launcher scripts using
Hi Uwe,
On Sat, Mar 8, 2014 at 5:17 PM, Uwe Schindler u...@thetaphi.de wrote:
[.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7 and backport all Java
7-related issues (FileChannel improvements, diamond operator,...).
+1 I think supporting 2 different versions is hard enough.
[.] Move
On Sat, Mar 8, 2014 at 11:17 AM, Uwe Schindler u...@thetaphi.de wrote:
[.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7
+1
[.] Move Lucene/Solr trunk to Java 8
-1 , I think it's too early for this.
-Yonik
http://heliosearch.org - native off-heap filters and fieldcache for solr
On Sat, Mar 8, 2014 at 11:41 AM, Adrien Grand jpou...@gmail.com wrote:
[.] Move Lucene/Solr trunk to Java 8 and allow closures in source code. This
would make some APIs much nicer. Our infrastructure mostly supports this,
only ECJ Javadoc linting is not yet possible, but forbidden-apis
On 3/8/2014 9:17 AM, Uwe Schindler wrote:
[.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7 and backport all Java
7-related issues (FileChannel improvements, diamond operator,...).
+1
We might want to wait until 4.9, so we can use the 4.8 release to
announce that the change is coming. My
Thanks Shawn for the support!
From: Shawn Heisey [mailto:s...@elyograg.org]
Sent: Saturday, March 08, 2014 8:23 PM
To: dev@lucene.apache.org
Subject: Re: [VOTE] Move to Java 7 in Lucene/Solr 4.8, use Java 8 in trunk
(once officially released)
On 3/8/2014 9:17 AM, Uwe Schindler wrote:
[.]
On Sat, Mar 8, 2014 at 9:47 PM, Uwe Schindler u...@thetaphi.de wrote:
[.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7 and backport all Java
7-related issues (FileChannel improvements, diamond operator,...).
+1
[.] Move Lucene/Solr trunk to Java 8 and allow closures in source code. This
31 matches
Mail list logo
