Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-23 Thread Martijn v Groningen
e is SOLR-10711. Do you >>>>>> consider it as a blocker? If so, can we mark it as such on the JIRA? Is >>>>>> there an issue for the Windows space issue? >>>>>> As for SOLR-10004, I don't think it is a release blocker; however a >>>>>

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-23 Thread Ishan Chattopadhyaya
Uwe, I've filed SOLR-10735 for the first issue you reported. Thanks, Ishan On Fri, May 19, 2017 at 12:30 PM, Uwe Schindler wrote: > I tried, > > the 6.6 branch and this test release has 2 problems: > > > >- The startup

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-23 Thread Ishan Chattopadhyaya
nsider it as a blocker? If so, can we mark it as such on the JIRA? Is >>>>> there an issue for the Windows space issue? >>>>> As for SOLR-10004, I don't think it is a release blocker; however a >>>>> nice one to fix before the re-spin, if possible. I'd be glad to >&g

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-23 Thread Martijn v Groningen
herwise. >>>> >>>> On Fri, May 19, 2017 at 6:40 PM, Christine Poerschke (BLOOMBERG/ >>>> LONDON) <cpoersc...@bloomberg.net> wrote: >>>> >>>>> The "javadocs want to fail" output sounds like >>>>> https://is

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-23 Thread Ishan Chattopadhyaya
, 2017 at 6:40 PM, Christine Poerschke (BLOOMBERG/ LONDON) >>> <cpoersc...@bloomberg.net> wrote: >>> >>>> The "javadocs want to fail" output sounds like >>>> https://issues.apache.org/jira/browse/SOLR-10004 ticket. >>>> >>>&

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-23 Thread Adrien Grand
7 at 6:40 PM, Christine Poerschke (BLOOMBERG/ LONDON) >> <cpoersc...@bloomberg.net> wrote: >> >>> The "javadocs want to fail" output sounds like >>> https://issues.apache.org/jira/browse/SOLR-10004 ticket. >>> >>> From: dev@lucene.a

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-22 Thread Ishan Chattopadhyaya
loomberg.net> wrote: > >> The "javadocs want to fail" output sounds like >> https://issues.apache.org/jira/browse/SOLR-10004 ticket. >> >> From: dev@lucene.apache.org At: 05/17/17 18:44:36 >> To: dev@lucene.apache.org >> Subject: Re: [VOTE] Rele

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-19 Thread Ishan Chattopadhyaya
//issues.apache.org/ > jira/browse/SOLR-10004 ticket. > > From: dev@lucene.apache.org At: 05/17/17 18:44:36 > To: dev@lucene.apache.org > Subject: Re: [VOTE] Release Lucene/Solr 6.6.0 RC1 > > The smoke tester ended with: > > SUCCESS! [0:59:34.797969] > > However, after loo

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-19 Thread Christine Poerschke (BLOOMBERG/ LONDON)
The "javadocs want to fail" output sounds like https://issues.apache.org/jira/browse/SOLR-10004 ticket. From: dev@lucene.apache.org At: 05/17/17 18:44:36 To: dev@lucene.apache.org Subject: Re: [VOTE] Release Lucene/Solr 6.6.0 RC1 The smoke tester ended with: SUCCESS! [0:59:34.797969

RE: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-19 Thread Uwe Schindler
I tried, the 6.6 branch and this test release has 2 problems: * The startup script (Windows at least) again does not work with whitepsace directory names, which is standard on Windows. It does give an error message not while server startup, but when trying to create the techproducts

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-19 Thread Adrien Grand
Ishan, I went ahead and merged to branch_6_6. If we were to decide to not respin I'll update the changes entry to move it to 6.6.1. Le jeu. 18 mai 2017 à 18:02, David Smiley a écrit : > > The fix looks low risk so I'd probably respin for it given there are > many users

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-18 Thread David Smiley
> The fix looks low risk so I'd probably respin for it given there are many users of block joins I think, +1 to incorporate and respin. Better to do this for newly found bugs than have yet another bugfix release. On Thu, May 18, 2017 at 11:16 AM Adrien Grand wrote: > Ishan,

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-18 Thread Adrien Grand
Ishan, a bug about scoring block join queries was just reported yesterday: https://issues.apache.org/jira/browse/LUCENE-7833. The fix looks low risk so I'd probably respin for it given there are many users of block joins I think, but I'll leave it up to you as a release manager. We can also do a

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-17 Thread Erik Hatcher
informal +1 - just fired up this RC1 and all was well with the payload support (SOLR-1485) with my use-case scripts. Erik > On May 17, 2017, at 9:49 AM, Ishan Chattopadhyaya wrote: > > Please vote for release candidate 1 for Lucene/Solr 6.6.0 > > The artifacts can

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-17 Thread Ishan Chattopadhyaya
> Something strange with the links in this message. They refer to both 6.6.0 and 6.5.0 ? It seems my copy paste of Joel's 6.5 announcement mail didn't affect the hyperlink, just pasted the text. I wish GMail was smarter. Here's the correct contents again: Please vote for release candidate 1

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-17 Thread David Smiley
The smoke tester ended with: SUCCESS! [0:59:34.797969] However, after looking at some of its output, I see a: ***WARNING***: javadocs want to fail! Which followed many "missing: ..." messages akin to this: unpack solr-6.6.0-src.tgz... make sure no JARs/WARs in src dist... run

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-17 Thread Andi Vajda
On Wed, 17 May 2017, Ishan Chattopadhyaya wrote: Please vote for release candidate 1 for Lucene/Solr 6.6.0 The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.6.0-RC1-rev4d055f00bba9a745737e4b6c3f9dff06dd35aa2e

Re: [VOTE] Release Lucene/Solr 6.6.0 RC1

2017-05-17 Thread Ishan Chattopadhyaya
For some reason, the artifacts didn't have the Lucene's .asc files copied over from the working directory to the artifact directory. The Solr ones were there. I copied them manually, and the smoke tester was happy again. I'll look into it as to why that could've happened. The raw logs