Re: Release a 6.6.1

imeError(msg) >> > RuntimeError: FAILED: ant -Dversion=6.6.1 -Dgpg.key=7F3DE8DA >> prepare-release [see log /tmp/release.log] >> > >> > Here's the release.log output : https://www.dropbox.com/s/yssv >> qbwcpjrq7ah/release.log?dl=0 which seems to indicat

Re: Release a 6.6.1

> I can backport it and then I'll begin working on the RC > > > > On Tue, Aug 22, 2017 at 2:17 AM, Uwe Schindler > <mailto:u...@thetaphi.de>> wrote: > > Hi, > > > > > > > > The windows startup script fix was committed to 7.0, but not

Re: Release a 6.6.1

ion=6.6.1 -Dgpg.key=7F3DE8DA >> prepare-release [see log /tmp/release.log] >> > >> > Here's the release.log output : https://www.dropbox.com/s/yssv >> qbwcpjrq7ah/release.log?dl=0 which seems to indicate that it succeeded ? >> > >> > >> > On Tue

Re: Release a 6.6.1

017 at 8:10 AM, Varun Thacker > wrote: > > Hi Uwe, > > > > I can backport it and then I'll begin working on the RC > > > > On Tue, Aug 22, 2017 at 2:17 AM, Uwe Schindler wrote: > > Hi, > > > > > > > > The windows startup script fix was

Re: Release a 6.6.1

> On Tue, Aug 22, 2017 at 2:17 AM, Uwe Schindler wrote: > Hi, > > > > The windows startup script fix was committed to 7.0, but not 6.6.1. If Varun > has time to test the fixes in https://issues.apache.org/jira/browse/SOLR-8689 > we may include them, but I left them out

Re: Release a 6.6.1

n Tue, Aug 22, 2017 at 8:10 AM, Varun Thacker >>>> wrote: >>>> >>>>> Hi Uwe, >>>>> >>>>> I can backport it and then I'll begin working on the RC >>>>> >>>>> On Tue, Aug 22, 2017 at 2:17 AM, Uwe Schi

Re: Release a 6.6.1

Aug 22, 2017 at 2:17 AM, Uwe Schindler wrote: >>>> >>>>> Hi, >>>>> >>>>> >>>>> >>>>> The windows startup script fix was committed to 7.0, but not 6.6.1. If >>>>> Varun has time to test the fixes in https:

Re: Release a 6.6.1

t;>> >>>> >>>> The windows startup script fix was committed to 7.0, but not 6.6.1. If >>>> Varun has time to test the fixes in https://issues.apache.org/jira >>>> /browse/SOLR-8689 we may include them, but I left them out for now. >>>>

Re: Release a 6.6.1

erry pick. >>> >>> >>> >>> Uwe >>> >>> >>> >>> - >>> >>> Uwe Schindler >>> >>> Achterdiek 19, D-28357 Bremen >>> >>> http://www.thetaphi.de >>> >>> eMail: u...@t

Re: Release a 6.6.1

t;> >> Uwe Schindler >> >> Achterdiek 19, D-28357 Bremen >> >> http://www.thetaphi.de >> >> eMail: u...@thetaphi.de >> >> >> >> *From:* Uwe Schindler [mailto:u...@thetaphi.de] >> *Sent:* Monday, August 21, 2017 2:11 PM >> &

Re: Release a 6.6.1

/www.thetaphi.de > > eMail: u...@thetaphi.de > > > > *From:* Uwe Schindler [mailto:u...@thetaphi.de] > *Sent:* Monday, August 21, 2017 2:11 PM > > *To:* dev@lucene.apache.org > *Subject:* RE: Release a 6.6.1 > > > > Hi, > > > > Is there any inter

RE: Release a 6.6.1

. Uwe - Uwe Schindler Achterdiek 19, D-28357 Bremen http://www.thetaphi.de <http://www.thetaphi.de/> eMail: u...@thetaphi.de From: Uwe Schindler [mailto:u...@thetaphi.de] Sent: Monday, August 21, 2017 2:11 PM To: dev@lucene.apache.org Subject: RE: Release a 6.6.1 Hi,

RE: Release a 6.6.1

M To: dev@lucene.apache.org Subject: Re: Release a 6.6.1 Hi Everyone, Does anyone plan on committing any more fixes to the release branch? I've disabled SOLR-11247 for the branch so that we get a few Jenkins runs without any failures. I plan on creating an RC in 12-14 hours ti

Re: Release a 6.6.1

system property temporarily on Java 9 while initializing >> Hadoop, which is not something you should ever do! >> >> >> >> Uwe >> >> >> >> - >> >> Uwe Schindler >> >> Achterdiek 19, D-28357 Bremen >> >> http://www.thetaphi

Re: Release a 6.6.1

t; Uwe > > > > - > > Uwe Schindler > > Achterdiek 19, D-28357 Bremen > > http://www.thetaphi.de > > eMail: u...@thetaphi.de > > > > *From:* Uwe Schindler [mailto:u...@thetaphi.de] > *Sent:* Sunday, August 20, 2017 12:53 PM > *To:* dev@lucene

RE: Release a 6.6.1

Uwe - Uwe Schindler Achterdiek 19, D-28357 Bremen http://www.thetaphi.de <http://www.thetaphi.de/> eMail: u...@thetaphi.de From: Uwe Schindler [mailto:u...@thetaphi.de] Sent: Sunday, August 20, 2017 12:53 PM To: dev@lucene.apache.org Subject: RE: Release a 6.6.1 Hi, I need to

RE: Release a 6.6.1

Sent: Saturday, August 19, 2017 12:00 AM To: dev@lucene.apache.org Subject: Re: Release a 6.6.1 Hi, I enabled Jenkins jobs on 👮. ASF was active already. Uwe Am 18. August 2017 23:34:23 MESZ schrieb Varun Thacker mailto:va...@vthacker.in> >: >From the bug fixes in lucene 7.0 do we n

Re: Release a 6.6.1

Thanks Uwe and Steve for enabling Jenkins for branch_6_6 and Adrien for confirming that no lucene issue requires backporting. On Sat, Aug 19, 2017 at 8:13 PM, Andrzej Białecki < andrzej.biale...@lucidworks.com> wrote: > > On 19 Aug 2017, at 11:24, Uwe Schindler wrote: > > Hi, > > No that's the r

Re: Release a 6.6.1

> On 19 Aug 2017, at 11:24, Uwe Schindler wrote: > > Hi, > > No that's the right branch. We tag releases from there. Whew, thanks. > > Uwe > > Am 19. August 2017 09:48:08 MESZ schrieb "Andrzej Białecki" > : > I accidentally pushed a back-port of SOLR-11221 to branch_6_6. This fix > shou

Re: Release a 6.6.1

Hi, No that's the right branch. We tag releases from there. Uwe Am 19. August 2017 09:48:08 MESZ schrieb "Andrzej Białecki" : >I accidentally pushed a back-port of SOLR-11221 to branch_6_6. This fix >should go into 6.6.1 - so should I revert it from branch_6_6? > >> On 18 Aug 2017, at 23:34, Va

Re: Release a 6.6.1

LUCENE-7914 should wait: it might fail automata that used to work before so I would not put in into a bugfix release. LUCENE-7871 has been introduced by dv iterators which are 7.0-only. >From LUCENE-7859's description, the issue arises with LUCENE-7845 which has only been merged to 7.0, so it sho

Re: Release a 6.6.1

I accidentally pushed a back-port of SOLR-11221 to branch_6_6. This fix should go into 6.6.1 - so should I revert it from branch_6_6? > On 18 Aug 2017, at 23:34, Varun Thacker wrote: > > From the bug fixes in lucene 7.0 do we need to backport any of these issues : > LUCENE-7859 / LUCENE-7871

Re: Release a 6.6.1

I enabled the 6.6 jobs on ASF Jenkins shortly after Varun emailed. I also enqueued them (though they won’t run until the previously enqueued jobs have run). While I was there I noticed that the Clover jobs were running (7x and master) on the two nodes, and they had both been running for days,

Re: Release a 6.6.1

Hi, I enabled Jenkins jobs on 👮. ASF was active already. Uwe Am 18. August 2017 23:34:23 MESZ schrieb Varun Thacker : >From the bug fixes in lucene 7.0 do we need to backport any of these >issues >: LUCENE-7859 / LUCENE-7871 / LUCENE-7914 ? > >I plan on backporting these three Solr fixes on Sun

Re: Release a 6.6.1

>From the bug fixes in lucene 7.0 do we need to backport any of these issues : LUCENE-7859 / LUCENE-7871 / LUCENE-7914 ? I plan on backporting these three Solr fixes on Sunday SOLR-10698 SOLR-10719 SOLR-11228 looking through the 7.0 bug fixes these two look important to get in as well : SOLR-1

Re: Release a 6.6.1

Right, that was the original note before we decided to backport a bunch of other stuff and I decided it made no sense to omit this one. All that has to happen is remove the " (note, not in 7.0, is in 7.1)" bits since it's in 6.6, 6.x, 7.0, 7.1 and master. Good catch! On Thu, Aug 17, 2017 at 3:1

Re: Release a 6.6.1

Should I then go remove the note part from the CHANGES entry in branch_6_6 ? * SOLR-11177: CoreContainer.load needs to send lazily loaded core descriptors to the proper list rather than send them all to the transient lists. (Erick Erickson) (note, not in 7.0, is in 7.1) I see a commit for this

Re: Release a 6.6.1

Well, it is in 7.0. Everything I moved to 6.6.1 is also in 7.0, or should be. On Thu, Aug 17, 2017 at 2:31 PM, Varun Thacker wrote: > Hi Erick, > > I was going through the CHANGES file from the 6_6 branch and just curious > why are we not planning on putting SOLR-11177 in 7.0 ? > > On Thu, Aug 17

Re: Release a 6.6.1

Hi Erick, I was going through the CHANGES file from the 6_6 branch and just curious why are we not planning on putting SOLR-11177 in 7.0 ? On Thu, Aug 17, 2017 at 7:45 AM, Erick Erickson wrote: > OK, I'm done with my changes for 7.0, I think Varun might have a few too. > > And things didn't mel

Re: Release a 6.6.1

OK, I'm done with my changes for 7.0, I think Varun might have a few too. And things didn't melt down overnight so... On Wed, Aug 16, 2017 at 12:25 PM, Anshum Gupta wrote: > +1 on getting the fixes into 7.0 if you are confident with those, and if > they are a part of 6.6.1. > > Thanks for taking

Re: Release a 6.6.1

+1 on getting the fixes into 7.0 if you are confident with those, and if they are a part of 6.6.1. Thanks for taking care of this Erick. On Wed, Aug 16, 2017 at 12:24 PM Erick Erickson wrote: > FYI: > > I'll be backporting the following to SOLR 7.0 today: > > SOLR-11024: ParallelStream should s

Re: Release a 6.6.1

FYI: I'll be backporting the following to SOLR 7.0 today: SOLR-11024: ParallelStream should set the StreamContext when constructing SolrStreams: SOLR-11177: CoreContainer.load needs to send lazily loaded core descriptors to the proper list rather than send them all to the transient lists. SOLR-11

Re: Release a 6.6.1

Yes, I’m confident in that patch and its safety, thanks Varun! Erik > On Aug 16, 2017, at 2:22 PM, Varun Thacker wrote: > > @Erik -If you are confident with the patch and if you think it's safe then > please go ahead and commit it. I'll try having a look at it tomorrow as well. > > I

Re: Release a 6.6.1

@Erik -If you are confident with the patch and if you think it's safe then please go ahead and commit it. I'll try having a look at it tomorrow as well. I will start back-porting issues which I am comfortable with. If others can chime in as well it will be great. I'll aim to cut an RC on Monday 2

Re: Release a 6.6.1

Hi Anshum, On Mon, Aug 14, 2017 at 5:42 PM, Anshum Gupta wrote: > +1 for a bug fix release. Do you plan to back port bug fixes from 7.1 too? > If so, I wouldn't want to release 7.0 without those fixes. > >From Lucene's change logs LUCENE-7916 is the only Jira which seems safe enough to backpo

Re: Release a 6.6.1

+1 for a bug fix release On Tue, Aug 15, 2017 at 6:56 AM, Erik Hatcher wrote: > I’d like to get https://issues.apache.org/jira/browse/SOLR-10874 in soon as > well. Varun, if you’d like to take this one over that’d be fine by me too > ;) otherwise prod me back channel and I’ll get to it. Ideall

Re: Release a 6.6.1

I’d like to get https://issues.apache.org/jira/browse/SOLR-10874 in soon as well. Varun, if you’d like to take this one over that’d be fine by me too ;) otherwise prod me back channel and I’ll get to it. Ideally I should have applied this one

Re: Release a 6.6.1

+1 for a bug fix release. Do you plan to back port bug fixes from 7.1 too? If so, I wouldn't want to release 7.0 without those fixes. On Mon, Aug 14, 2017 at 2:51 PM Varun Thacker wrote: > From the change log of 6.7 / 7.0 and 7.1 the total count of bug fixes > under lucene and solr are > > Luce

Re: Release a 6.6.1

+1 of course. On Mon, Aug 14, 2017 at 2:51 PM, Varun Thacker wrote: > From the change log of 6.7 / 7.0 and 7.1 the total count of bug fixes under > lucene and solr are > > Lucene : 7 > Solr : 61 > > > I'd be happy to volunteer as a release manager for a bug fix 6.6.1 release > if others in the co

Release a 6.6.1

>From the change log of 6.7 / 7.0 and 7.1 the total count of bug fixes under lucene and solr are Lucene : 7 Solr : 61 I'd be happy to volunteer as a release manager for a bug fix 6.6.1 release if others in the community think it's a good idea