Re: 5.3 release

Figured it out and downgraded to a trivial bug. -Yonik On Wed, Aug 12, 2015 at 1:57 PM, Yonik Seeley wrote: > I've set this as a blocker until we know more about the actual impact. > https://issues.apache.org/jira/browse/SOLR-7917 > > -Yonik > > > On Tue, Aug 11, 2015 at 12:49 PM, Noble Paul wro

Re: 5.3 release

I'm done with the blockers. Planning to cut an RC soon. --Noble On Tue, Aug 11, 2015 at 7:08 PM, Shalin Shekhar Mangar wrote: > Yeah, sorry Mike. I wasn't sure of the protocol here. I'll keep that > in mind from the next time. > > On Tue, Aug 11, 2015 at 3:18 AM, Michael McCandless > wrote: >> O

Re: 5.3 release

Yeah, sorry Mike. I wasn't sure of the protocol here. I'll keep that in mind from the next time. On Tue, Aug 11, 2015 at 3:18 AM, Michael McCandless wrote: > On Mon, Aug 10, 2015 at 5:30 PM, Chris Hostetter > wrote: >> >> : I'm confused: this issue isn't a blocker? Why are we holding up a >> :

Re: 5.3 release

I opened SOLR-7909 yesterday as blocker to flag that ZK ACL cannot be setup through VM-params as documented. The fix looks simple, but an alternative for 5.3 is to change the documentation since there is a known workaround using solr.xml. Will do some testing. -- Jan Høydahl, search solution ar

Re: 5.3 release

I've committed a trivial logging/nocommit statement removal (SOLR-7911). I hope that is ok. On Mon, Jul 27, 2015 at 1:56 AM, Noble Paul wrote: > Hi, > I would like to volunteer myself as the RM for 5.3 release. I plan to > cut the 5.3 release branch by next Monday (03/Aug). > > -- >

Re: 5.3 release

On Mon, Aug 10, 2015 at 5:30 PM, Chris Hostetter wrote: > > : I'm confused: this issue isn't a blocker? Why are we holding up a > : release for non-blocker issues? > > If i understand correctly, SOLR-7838 is (part of) a "feature" and by > definition not a blocker -- but after being committed Shal

Re: 5.3 release

: I'm confused: this issue isn't a blocker? Why are we holding up a : release for non-blocker issues? If i understand correctly, SOLR-7838 is (part of) a "feature" and by definition not a blocker -- but after being committed Shalin noticed that the "syntax" of the user facing API introduced in

Re: 5.3 release

I'm confused: this issue isn't a blocker? Why are we holding up a release for non-blocker issues? Mike McCandless http://blog.mikemccandless.com On Mon, Aug 10, 2015 at 1:51 PM, Noble Paul wrote: > I reopened https://issues.apache.org/jira/browse/SOLR-7838 > Need to incorporate the syntax cha

Re: 5.3 release

I reopened https://issues.apache.org/jira/browse/SOLR-7838 Need to incorporate the syntax changes. I'll cut the firs release candidate after that On Mon, Aug 10, 2015 at 9:33 PM, Erik Hatcher wrote: > I knew things were stalled so I slipped SOLR-7900 in to 5.3. (this is > example/files stuff th

Re: 5.3 release

I knew things were stalled so I slipped SOLR-7900 in to 5.3. (this is example/files stuff that is soon to be publicized more, so wanted to be sure the latest stuff made it to next release). — Erik Hatcher, Senior Solutions Architect http://www.lucidworks.com

Re: 5.3 release

Ok. Many thanks! I was not sure, I think I removed the workspaces using the Gui after disabling them. I just wanted to be sure we not run out of disk space. Uwe Am 7. August 2015 21:02:39 MESZ, schrieb Steve Rowe : > >> On Aug 7, 2015, at 2:50 PM, Steve Rowe wrote: >> On Aug 5, 2015, at

Re: 5.3 release

> On Aug 7, 2015, at 2:50 PM, Steve Rowe wrote: > >>> On Aug 5, 2015, at 3:10 PM, Uwe Schindler wrote: >>> >>> Steve: For ASF Jenkins, it would be ideal to rename the preexisting 5.2 >>> jobs and simply change the branch in the subversion settings. Before doing >>> that, be sure to delete th

Re: 5.3 release

I have merged/committed SOLR-7877 and SOLR-7766 to lucene_solr_5_3 branch. cwiki.apache.org also updated now w.r.t. SOLR-7766. --Christine - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org Cc: sar...@gmail.com, u...@thetaphi.de At: Aug 5 2015 16:10:09 I have cr

Re: 5.3 release

> On Aug 5, 2015, at 3:25 PM, Steve Rowe wrote: > > Uwe, I don’t think renaming the preexisting 5.2 jobs is ideal, because > preexisting release branch jobs can have stale config (inactive jobs’ configs > don’t always get updated when other jobs’ configs do). When setting up > release branch

Re: 5.3 release

Eeeks. Cause is obvious actually. The checkout I made of 5.3 was http, not https. Will make my commit now. Upayavira On Thu, Aug 6, 2015, at 12:29 PM, Upayavira wrote: > Yes, it *should* work. Hopefully someone'll make the commit whilst I > ask on infra@ to understand why this is breaking. > > T

Re: 5.3 release

Yes, it *should* work. Hopefully someone'll make the commit whilst I ask on infra@ to understand why this is breaking. Thx! On Thu, Aug 6, 2015, at 11:52 AM, Uwe Schindler wrote: > This should work without error 503. Maybe a temporary problem with > subversion server? > > Uwe > > Am 6. August 20

Re: 5.3 release

This should work without error 503. Maybe a temporary problem with subversion server? Uwe Am 6. August 2015 11:49:25 MESZ, schrieb Upayavira : >I just committed this to trunk and the lucene_5x branch. However, when >I >attempted to commit it to the lucene/dev/branches/lucene_solr_5_3 >branch, I

Re: 5.3 release

I just committed this to trunk and the lucene_5x branch. However, when I attempted to commit it to the lucene/dev/branches/lucene_solr_5_3 branch, I got this error: svn: E175013: Commit failed (details follow): svn: E175013: POST of '/repos/asf/!svn/me': 403 Forbidden (http://svn.apache.org) svn:

Re: 5.3 release

Noble Paul [2015-08-05 17:09]: If anything new must go into 5.3 release please communicate it here What are the chances of getting the second patch from SOLR-7639 included in this release? It adds the missing pieces (support for the `boost` parameter and exclusion of the current document from t

Re: 5.3 release

.de > eMail: u...@thetaphi.de > > >> -Original Message- >> From: Steve Rowe [mailto:sar...@gmail.com] >> Sent: Wednesday, August 05, 2015 5:16 PM >> To: Lucene Dev >> Cc: Uwe Schindler; Noble Paul >> Subject: Re: 5.3 release >> >> I c

RE: 5.3 release

.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Steve Rowe [mailto:sar...@gmail.com] > Sent: Wednesday, August 05, 2015 5:16 PM > To: Lucene Dev > Cc: Uwe Schindler; Noble Paul > Subject: Re: 5.3 release > &g

Re: 5.3 release

Figured out the SOLR-7877 issue, patch to follow. - Original Message - From: dev@lucene.apache.org To: dev@lucene.apache.org At: Aug 5 2015 18:39:45 I have opened this ticket to track the test failures https://issues.apache.org/jira/browse/SOLR-7877 On Wed, Aug 5, 2015 at 11:04 PM, Nob

Re: 5.3 release

I have opened this ticket to track the test failures https://issues.apache.org/jira/browse/SOLR-7877 On Wed, Aug 5, 2015 at 11:04 PM, Noble Paul wrote: > Which is the JIRA? > > On Wed, Aug 5, 2015 at 9:00 PM, Upayavira wrote: >> I need to update CHANGES.txt to account for a number of bug fixes

Re: 5.3 release

Which is the JIRA? On Wed, Aug 5, 2015 at 9:00 PM, Upayavira wrote: > I need to update CHANGES.txt to account for a number of bug fixes to the > angular UI. I'll add a single entry to account for them all. > > Upayavira > > On Wed, Aug 5, 2015, at 04:15 PM, Steve Rowe wrote: >> I can work on sett

Re: 5.3 release

I need to update CHANGES.txt to account for a number of bug fixes to the angular UI. I'll add a single entry to account for them all. Upayavira On Wed, Aug 5, 2015, at 04:15 PM, Steve Rowe wrote: > I can work on setting up 5.3 release branch jobs on ASF Jenkins later > today if Uwe doesn’t beat m

Re: 5.3 release

I can work on setting up 5.3 release branch jobs on ASF Jenkins later today if Uwe doesn’t beat me to it. - Steve > On Aug 5, 2015, at 11:09 AM, Noble Paul wrote: > > I have created the lucene_solr_5_3 branch. > If anything new must go into 5.3 release please communicate it here > and commit to

Re: 5.3 release

I have created the lucene_solr_5_3 branch. If anything new must go into 5.3 release please communicate it here and commit to the new branch as well @uwe, @sarowe , can someone help me setup jenkins for the same. --Noble On Wed, Aug 5, 2015 at 7:27 PM, Varun Thacker wrote: > Hi Noble, > > I've ju

Re: 5.3 release

Hi Noble, I've just now committed SOLR-7818 and SOLR-7756. Both were bug fixes. I'm done from my side for 5.3 On Wed, Aug 5, 2015 at 1:22 PM, Noble Paul wrote: > https://issues.apache.org/jira/browse/SOLR-7692 is slated to be a part > of 5.3 . I'm wrapping it up. > As you suggested , it makes s

Re: 5.3 release

https://issues.apache.org/jira/browse/SOLR-7692 is slated to be a part of 5.3 . I'm wrapping it up. As you suggested , it makes sense to cut a branch and stabilize stuff. I shall cut a branch as soon as possible I guess there could be other things too. --Noble On Tue, Aug 4, 2015 at 6:55 PM, Adri

Re: 5.3 release

Hi Noble, Which changes are delaying the branch creation? Even if everything that we want for 5.3 is not ready yet, it could be useful to create the branch now to help stabilize it? We could still merge the changes we want in after the branch is created. On Mon, Aug 3, 2015 at 4:52 PM, Noble Paul

Re: 5.3 release

I may have to push the branch by a day or two. There are some more loose ends to be tied up from my side. Sorry for the trouble --Noble On Thu, Jul 30, 2015 at 12:48 PM, Adrien Grand wrote: > +1 to releasing 5.3, and thanks for volunteering! > > On Mon, Jul 27, 2015 at 10:56 AM, Noble Paul wrot

Re: 5.3 release

+1 to releasing 5.3, and thanks for volunteering! On Mon, Jul 27, 2015 at 10:56 AM, Noble Paul wrote: > Hi, > I would like to volunteer myself as the RM for 5.3 release. I plan to > cut the 5.3 release branch by next Monday (03/Aug). > > -- > -