[RESULT][VOTE] Release Lucene/Solr 6.0.1 RC2

16 at 9:43 AM, Steve Rowe <sar...@gmail.com> wrote: > Please vote for release candidate 2 for Lucene/Solr 6.0.1. (I found a couple > problems in CHANGES after I committed RC1 to Subversion, so I didn’t call the > vote, and cut RC2 instead.) > > The artifacts can be downloade

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

+1 SUCCESS! [1:10:04.644047] On Tue, May 24, 2016 at 9:43 AM, Steve Rowe <sar...@gmail.com> wrote: > Please vote for release candidate 2 for Lucene/Solr 6.0.1. (I found a > couple problems in CHANGES after I committed RC1 to Subversion, so I didn’t > call the vote, and

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

+1 SUCCESS! [0:55:13.784752] Le jeu. 26 mai 2016 à 08:49, Tomás Fernández Löbbe a écrit : > +1 > SUCCESS! [1:13:52.067157] > > On Wed, May 25, 2016 at 2:52 PM, Michael McCandless < > luc...@mikemccandless.com> wrote: > >> Thanks Steve. >> >> Mike McCandless >> >>

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

+1 SUCCESS! [1:13:52.067157] On Wed, May 25, 2016 at 2:52 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > Thanks Steve. > > Mike McCandless > > http://blog.mikemccandless.com > > On Wed, May 25, 2016 at 4:45 PM, Steve Rowe wrote: > >> >> > On May 25, 2016, at

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

Thanks Steve. Mike McCandless http://blog.mikemccandless.com On Wed, May 25, 2016 at 4:45 PM, Steve Rowe wrote: > > > On May 25, 2016, at 11:27 AM, David Smiley > wrote: > > > > The problem I had was that I was on branch_6x not the release branch.

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

> On May 25, 2016, at 11:27 AM, David Smiley wrote: > > The problem I had was that I was on branch_6x not the release branch. I > thought it'd be good enough but apparently not. > > On Wed, May 25, 2016 at 9:13 AM Steve Rowe wrote: > >> On May

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

doing the release, Steve. All looks good to me but I think > you should get someone to sign you GPG key :) > > > > I see this warning while running the tests: GPG: gpg: WARNING: This key > is not certified with a trusted signature! > > > > Here's my +1! > > &g

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

+1 -Yonik On Tue, May 24, 2016 at 12:13 AM, Steve Rowe <sar...@gmail.com> wrote: > Please vote for release candidate 2 for Lucene/Solr 6.0.1. (I found a couple > problems in CHANGES after I committed RC1 to Subversion, so I didn’t call the > vote, and cut RC2 instead.) > &

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

+1 SUCCESS! [0:49:14.757238] The problem I had was that I was on branch_6x not the release branch. I thought it'd be good enough but apparently not. On Wed, May 25, 2016 at 9:13 AM Steve Rowe wrote: > Hi David, > > I think this is a result of the JDK naming stuff that Uwe

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

Hi David, I think this is a result of the JDK naming stuff that Uwe has been working on (e.g. 1.8->8) to enable JDK9 usage - but AFAIK that’s not on branch_6_0: > On May 25, 2016, at 12:48 AM, David Smiley wrote: > [...] > RuntimeError: JAR file >

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

hile running the tests: GPG: gpg: WARNING: This key is > not certified with a trusted signature! > > Here's my +1! > > SUCCESS! [1:05:50.755245] > > > > On Tue, May 24, 2016 at 5:24 AM, Michael McCandless > <luc...@mikemccandless.com> wrote: > +1 > &

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

ning while running the tests: GPG: gpg: WARNING: This key >> is not certified with a trusted signature! >> >> Here's my +1! >> >> SUCCESS! [1:05:50.755245] >> >> >> >> On Tue, May 24, 2016 at 5:24 AM, Michael McCandless < >> luc...@

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

>>not certified with a trusted signature! >> >> >>Here's my +1! >> >> >>SUCCESS! [1:05:50.755245] >> >> >> >> >> >> >> >>On Tue, May 24, 2016 at 5:24 AM, Michael McCandless >><luc...@mikemcc

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

CESS! [1:05:50.755245] >> >> >> >> On Tue, May 24, 2016 at 5:24 AM, Michael McCandless < >> luc...@mikemccandless.com> wrote: >> >>> +1 >>> >>> SUCCESS! [0:31:57.451386] >>> >>> Mike McCandless

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

ture! > > Here's my +1! > > SUCCESS! [1:05:50.755245] > > > > On Tue, May 24, 2016 at 5:24 AM, Michael McCandless < > luc...@mikemccandless.com> wrote: > >> +1 >> >> SUCCESS! [0:31:57.451386] >> >> Mike McCandless >> >> http://blog.mikem

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

at 5:24 AM, Michael McCandless < luc...@mikemccandless.com> wrote: > +1 > > SUCCESS! [0:31:57.451386] > > Mike McCandless > > http://blog.mikemccandless.com > > On Tue, May 24, 2016 at 12:13 AM, Steve Rowe <sar...@gmail.com> wrote: > >> Please vote fo

Re: [VOTE] Release Lucene/Solr 6.0.1 RC2

+1 SUCCESS! [0:31:57.451386] Mike McCandless http://blog.mikemccandless.com On Tue, May 24, 2016 at 12:13 AM, Steve Rowe <sar...@gmail.com> wrote: > Please vote for release candidate 2 for Lucene/Solr 6.0.1. (I found a > couple problems in CHANGES after I committed RC1 to Subv

[VOTE] Release Lucene/Solr 6.0.1 RC2

Please vote for release candidate 2 for Lucene/Solr 6.0.1. (I found a couple problems in CHANGES after I committed RC1 to Subversion, so I didn’t call the vote, and cut RC2 instead.) The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.0.1-RC2

Re: Lucene/Solr 6.0.1

ng with the backports. >> >> Uwe >> >> - >> Uwe Schindler >> H.-H.-Meier-Allee 63, D-28213 Bremen >> http://www.thetaphi.de >> eMail: u...@thetaphi.de >> >>> -Original Message- >>> From: Steve Rowe [mailto:sar.

Re: Lucene/Solr 6.0.1

om] >> Sent: Saturday, May 21, 2016 2:04 AM >> To: Lucene Dev <dev@lucene.apache.org> >> Subject: Re: Lucene/Solr 6.0.1 >> >> Progress: >> >> I have finished backporting existing 5.5.1 and 6.1 LUCENE and SOLR bugfixes. >> >> I plan on delay

RE: Lucene/Solr 6.0.1

> -Original Message- > From: Steve Rowe [mailto:sar...@gmail.com] > Sent: Saturday, May 21, 2016 2:04 AM > To: Lucene Dev <dev@lucene.apache.org> > Subject: Re: Lucene/Solr 6.0.1 > > Progress: > > I have finished backporting existing 5.5.1 and 6.1 LUCENE and SOLR bugfix

Re: Lucene/Solr 6.0.1

Progress: I have finished backporting existing 5.5.1 and 6.1 LUCENE and SOLR bugfixes. I plan on delaying 6.0.1 RC creation until Monday May 23, in the morning US Eastern - that’ll give time for the backported changes to soak on Jenkins. -- Steve www.lucidworks.com > On May 13, 2016, at 8:16

Re: Lucene/Solr 6.0.1

Thanks Robert, I won’t backport them. -- Steve .lucidworks.com > On May 20, 2016, at 3:16 PM, Robert Muir wrote: > > I think those would be risky to backport, there was a lot of > refactoring and cleanup across many issues. Some of the fixes relied > on fixing the

Re: Lucene/Solr 6.0.1

I think those would be risky to backport, there was a lot of refactoring and cleanup across many issues. Some of the fixes relied on fixing the encoding and things like that. On Fri, May 20, 2016 at 2:53 PM, Steve Rowe wrote: > Thanks Mike, sounds good. > > BTW, (CC’ing Robert

Re: Lucene/Solr 6.0.1

Thanks Mike, sounds good. BTW, (CC’ing Robert too), I tried to backport the following 6.1 bugfixes, but cherry-picking the branch_6x commits into branch_6_0 wasn’t clean ("both modified” for several files for each issue) - do you think they’re worthy/capable of being backported?: *

Re: Lucene/Solr 6.0.1

Hi Steve, I think we should also fix https://issues.apache.org/jira/browse/LUCENE-7293 for 6.0.1 ... I'll commit shortly. Mike McCandless http://blog.mikemccandless.com On Sun, May 15, 2016 at 12:20 AM, Steve Rowe wrote: > Yes, I will fix up trunk and branch_6x CHANGES.txt

Re: Lucene/Solr 6.0.1

Yes, I will fix up trunk and branch_6x CHANGES.txt for backported issues. -- Steve www.lucidworks.com > On May 14, 2016, at 12:33 AM, David Smiley wrote: > > Oh right, of course :-) So I cherry picked those over to the 6.0 branch. > The Lucene one is strictly

Re: Lucene/Solr 6.0.1

Oh right, of course :-) So I cherry picked those over to the 6.0 branch. The Lucene one is strictly speaking a "new feature" but it's to make the GCD configurable necessary to enable the Solr-side to use it without a GCD. At some point after the release I presume you'll sync up the CHANGES.txt

Re: Lucene/Solr 6.0.1

Progress: I added the 6.0.1 version where it should be, and I checked in backcompat indexes for 6.0.0, so the smoke checker should now succeed. I’ve re-enabled the 6.0 branch jobs on ASF Jenkins and on my Jenkins. Uwe, would you please re-enable the Policeman Jenkins 6.0 release branch jobs?

Re: Lucene/Solr 6.0.1

David, Since it’s a bugfix release, the branch is already cut: branch_6_0. Please go ahead and start backporting whenever you’re ready. -- Steve www.lucidworks.com > On May 13, 2016, at 12:24 PM, David Smiley wrote: > > When you cut the branch, I'll port the

Re: Lucene/Solr 6.0.1

There are a collection of minor UI patches languishing in JIRA that it would be good to get out there too. I will endeavour to get them into Git before Friday. Upayavira On Fri, 13 May 2016, at 06:07 PM, Steve Rowe wrote: > Good idea, Adrien, but: I want to include SOLR-8992 in a 6.0.x release -

Re: Lucene/Solr 6.0.1

Good idea, Adrien, but: I want to include SOLR-8992 in a 6.0.x release - it restores functionality unintentionally removed in 6.0. -- Steve www.lucidworks.com > On May 13, 2016, at 12:53 PM, Adrien Grand wrote: > > Hi Steve, > > I think it is about time to do a 6.1 release

Re: Lucene/Solr 6.0.1

Hi Steve, I think it is about time to do a 6.1 release as well since we have some nice pending improvements. So if that would cover your needs too, maybe we could skip 6.0.1 and do a 6.1 directly to save some work? This is not an objection to doing a 6.0.1 release, I just wanted to throw out the

Re: Lucene/Solr 6.0.1

When you cut the branch, I'll port the "gregorian change date" bugs/issues (2 Solr, 1 Lucene). On Fri, May 13, 2016 at 12:06 PM Steve Rowe wrote: > I’d like to make a 6.0.1 release, and I volunteer to be RM. > > I propose to cut the first RC in one week: next Friday. > > -- >

Lucene/Solr 6.0.1

I’d like to make a 6.0.1 release, and I volunteer to be RM. I propose to cut the first RC in one week: next Friday. -- Steve www.lucidworks.com - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands,