Re: [VOTE] Release Lucene/Solr 5.5.1

n Grand <jpou...@gmail.com> >>>>> wrote: >>>>> >>>>>> +1 SUCCESS! [0:57:52.080980] >>>>>> >>>>>> Le mar. 3 mai 2016 à 19:36, Anshum Gupta <ans...@anshumgupta.net> a &g

[RESULT] Lucene/Solr 5.5.1 RC1 Release vote

The release vote for Lucene/Solr 5.5.1 RC1 has passed. I will work on publishing it tomorrow. Thanks to everyone who voted and helped with the release process! -- Anshum Gupta

Re: [VOTE] Release Lucene/Solr 5.5.1

om> >>>> wrote: >>>> >>>>> +1 SUCCESS! [0:57:52.080980] >>>>> >>>>> Le mar. 3 mai 2016 à 19:36, Anshum Gupta <ans...@anshumgupta.net> a >>>>> écrit : >>>>> >>>>>> FYI,

Re: [VOTE] Release Lucene/Solr 5.5.1

80980] >>>> >>>> Le mar. 3 mai 2016 à 19:36, Anshum Gupta <ans...@anshumgupta.net> a >>>> écrit : >>>> >>>>> FYI, we generally don't consider weekends for the 72 hour window so >>>>> we'd be waiting until Wedn

Re: [VOTE] Release Lucene/Solr 5.5.1

ut. >>>> Thought I'd let everyone who's waiting know about this. >>>> >>>> On Sat, Apr 30, 2016 at 2:25 PM, Anshum Gupta <ans...@anshumgupta.net> >>>> wrote: >>>> >>>>> Please vote for the RC1 release candidate for Lucen

Re: [VOTE] Release Lucene/Solr 5.5.1

> On May 4, 2016, at 11:50 AM, Michael McCandless > wrote: > > Lucene is perfect and has no bugs. The correct form of that statement is “the Lucene test suite is inadequate.” :-) wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my

Re: [VOTE] Release Lucene/Solr 5.5.1

ne out. >>> Thought I'd let everyone who's waiting know about this. >>> >>> On Sat, Apr 30, 2016 at 2:25 PM, Anshum Gupta <ans...@anshumgupta.net> >>> wrote: >>> >>>> Please vote for the RC1 release candidate for Lucene/Solr 5.5.1. >&

Re: [VOTE] Release Lucene/Solr 5.5.1

waiting know about this. >> >> On Sat, Apr 30, 2016 at 2:25 PM, Anshum Gupta <ans...@anshumgupta.net> >> wrote: >> >>> Please vote for the RC1 release candidate for Lucene/Solr 5.5.1. >>> >>> Artifacts: >>> >>> https://dist

Re: [VOTE] Release Lucene/Solr 5.5.1

ting know about this. > > On Sat, Apr 30, 2016 at 2:25 PM, Anshum Gupta <ans...@anshumgupta.net> > wrote: > >> Please vote for the RC1 release candidate for Lucene/Solr 5.5.1. >> >> Artifacts: >> >> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.

Re: [VOTE] Release Lucene/Solr 5.5.1

1 release candidate for Lucene/Solr 5.5.1. > > Artifacts: > > https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.5.1-RC1-revc08f17bca0d9cbf516874d13d221ab100e5b7d58 > > Smoke tester: > > python3 -u dev-tools/scripts/smokeTestRelease.py > https://dist.apache.org/rep

Re: [VOTE] Release Lucene/Solr 5.5.1

;noble.p...@gmail.com> wrote: > I shall dig into this > > On Mon, May 2, 2016 at 9:17 PM, Yonik Seeley <ysee...@gmail.com> wrote: > >> +1 >> >> -Yonik >> >> >> On Sat, Apr 30, 2016 at 5:25 PM, Anshum Gupta <ans...@anshumgupta.net> >>

Re: [VOTE] Release Lucene/Solr 5.5.1

I shall dig into this On Mon, May 2, 2016 at 9:17 PM, Yonik Seeley <ysee...@gmail.com> wrote: > +1 > > -Yonik > > > On Sat, Apr 30, 2016 at 5:25 PM, Anshum Gupta <ans...@anshumgupta.net> > wrote: > > Please vote for the RC1 release candidate for Lucene/Sol

Re: [VOTE] Release Lucene/Solr 5.5.1

+1 -Yonik On Sat, Apr 30, 2016 at 5:25 PM, Anshum Gupta <ans...@anshumgupta.net> wrote: > Please vote for the RC1 release candidate for Lucene/Solr 5.5.1. > > Artifacts: > https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.5.1-RC1-revc08f17bca0d9cbf516874d13d221ab10

Re: [VOTE] Release Lucene/Solr 5.5.1

+1 Docs, changes and javadocs look good. The smoke tester passed for me (with java8): SUCCESS! [0:45:46.037606] -- Steve www.lucidworks.com > On Apr 30, 2016, at 5:25 PM, Anshum Gupta <ans...@anshumgupta.net> wrote: > > Please vote for the RC1 release candidate for Lu

Re: [VOTE] Release Lucene/Solr 5.5.1

+1 SUCCESS! [0:51:00.367685] On Sat, Apr 30, 2016 at 3:25 PM, Anshum Gupta <ans...@anshumgupta.net> wrote: > Please vote for the RC1 release candidate for Lucene/Solr 5.5.1. > > Artifacts: > https://dist.apache.org/repos/dist/dev/lucene/luc

Re: [VOTE] Release Lucene/Solr 5.5.1

o dig into the failure, so I > can't tell if it should hold off the release. What do you think? > > Shai > > On Sun, May 1, 2016 at 12:26 AM Anshum Gupta <ans...@anshumgupta.net> > wrote: > >> Please vote for the RC1 release candidate for Lucene/Solr 5.5.1. >> &g

Re: [VOTE] Release Lucene/Solr 5.5.1

Shai On Sun, May 1, 2016 at 12:26 AM Anshum Gupta <ans...@anshumgupta.net> wrote: > Please vote for the RC1 release candidate for Lucene/Solr 5.5.1. > > Artifacts: > > https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.5.1-RC1-revc08f17bca0d9cbf516874d13d221ab100e5b7d58 &g

[VOTE] Release Lucene/Solr 5.5.1

Please vote for the RC1 release candidate for Lucene/Solr 5.5.1. Artifacts: https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-5.5.1-RC1-revc08f17bca0d9cbf516874d13d221ab100e5b7d58 Smoke tester: python3 -u dev-tools/scripts/smokeTestRelease.py https://dist.apache.org/repos/dist/dev

Re: Lucene/Solr 5.5.1

I tried to add the back compat index for 5.5.0 by running the script on branch_5x, but it errors out when running the test with : "Extra back-compat test files: 5.5.0-cfs". I'm confused here in terms of what the instructions say and what's supposed to be done. On Fri, Apr 29, 2016 at 6:52 PM,

Re: Lucene/Solr 5.5.1

Seems like 5.5.0 back compat index was never added. Can someone confirm that? I have the RC but the smoke test failed when I ran it locally. Here's the error: Verify... confirm all releases have coverage in TestBackwardsCompatibility find all past Lucene releases... run

Re: Lucene/Solr 5.5.1

Something seems to be going on with TestManagedSchemaAPI as it's been consistently failing. I woke up with a fever today so I'll try and debug it some time later if I'm unable to get an RC built, but if I do get the RC, I'll get it out to vote and in parallel see if it's something that needs

Re: Lucene/Solr 5.5.1

That makes sense considering there are those checks for ignoring 1 missing version. On Fri, Apr 29, 2016 at 6:53 AM, Steve Rowe wrote: > Anshum, > > TL;DR: When there is only one release in flight, I think it’s okay to run > addVersion.py on all branches at the start of the

Re: Lucene/Solr 5.5.1

Hi Upayavira, I've already started the release process and I'm creating an RC. It would've been created last night but the tests failed so I'm just creating it again. Feel free to commit this to 5.5 so that if we re-spin for whatever reason, this would get automatically included unless you think

Re: Lucene/Solr 5.5.1

Anshum, TL;DR: When there is only one release in flight, I think it’s okay to run addVersion.py on all branches at the start of the release process for all types of releases. When we chatted last night I said backcompat index testing was a problem on non-release branches in the interval

Re: Lucene/Solr 5.5.1

I would like to include at least one, possibly two, trivial but significant fixes to the Solr Admin UI - SOLR-9032 is one of them, where the create alias feature fails without telling you. I'll try to get this committed by the end of the weekend. Upayavira On Fri, 29 Apr 2016, at 03:44 AM,

Re: Lucene/Solr 5.5.1

I've updated the "Update Version Numbers in the Source Code" section on the ReleaseToDo page. It'd be good to have some one else also take a look at it. Here is what I've changed (only bug fix release): * Only bump up the version on the release branch using addVersion.py * Don't bump it up on the

Re: Lucene/Solr 5.5.1

That's fixed (about to commit the fix from LUCENE-7265) thought. While discussing the release process, Steve mentioned that we should document the failing back-compat index test on the non-release branches due to the missing index for the unreleased version. On discussing further, he suggested

Re: Lucene/Solr 5.5.1

Seems like LUCENE-6938 removed the merge logic that used the change id. Now the merge doesn't happen, and there's no logic that replaces it. I certainly can do with some help on this one. On Thu, Apr 28, 2016 at 11:24 AM, Anshum Gupta wrote: > Just wanted to make sure I

Re: Lucene/Solr 5.5.1

Just wanted to make sure I wasn't missing something here again. While trying to update the version on 5x, after having done that on 5.5, using the addVersion.py script and following the instructions, the command consistently fails. Here's what I've been trying to do: python3 -u

Re: Lucene/Solr 5.5.1

Too much going on! Thanks Yonik. I'll start working on the RC now. NOTE: Please don't back port any more issues right now. In case of exceptions, please raise them here. On Thu, Apr 28, 2016 at 9:09 AM, Yonik Seeley wrote: > On Thu, Apr 28, 2016 at 12:04 PM, Anshum Gupta

Re: Lucene/Solr 5.5.1

On Thu, Apr 28, 2016 at 12:04 PM, Anshum Gupta wrote: > Thanks. I'm waiting for the last back port of SOLR-8865. It should be already be there... I closed it yesterday. -Yonik - To unsubscribe, e-mail:

Re: Lucene/Solr 5.5.1

Thanks. I'm waiting for the last back port of SOLR-8865. On Wed, Apr 27, 2016 at 4:55 PM, Steve Rowe wrote: > Anshum, > > FYI, I finished backporting SOLR-8082. > > -- > Steve > www.lucidworks.com > > > On Apr 27, 2016, at 6:58 PM, Anshum Gupta >

Re: Lucene/Solr 5.5.1

Anshum, FYI, I finished backporting SOLR-8082. -- Steve www.lucidworks.com > On Apr 27, 2016, at 6:58 PM, Anshum Gupta wrote: > > FYI, I'll wait until Uwe commits SOLR-9046 and then have the RC out. > > On Wed, Apr 27, 2016 at 1:08 PM, Anshum Gupta

Re: Lucene/Solr 5.5.1

FYI, I'll wait until Uwe commits SOLR-9046 and then have the RC out. On Wed, Apr 27, 2016 at 1:08 PM, Anshum Gupta wrote: > Thanks for clarifying Steve. I'll try it out when I'm ready. There are > still 2 issues I'm waiting on. > > > On Wed, Apr 27, 2016 at 12:55 PM,

Re: Lucene/Solr 5.5.1

Thanks for clarifying Steve. I'll try it out when I'm ready. There are still 2 issues I'm waiting on. On Wed, Apr 27, 2016 at 12:55 PM, Steve Rowe wrote: > So the general idea is to add the version-to-be-released on every branch > from which a version will likely be cut in

Re: Lucene/Solr 5.5.1

So the general idea is to add the version-to-be-released on every branch from which a version will likely be cut in the future. In this case that includes 5_5, 5x, 6_0, 6x, and master. I think you should run addVersion.py on 6_0, since a 6.0.1 release seems quite likely, but the script

Re: Lucene/Solr 5.5.1

Hi Karthik, I would like to have the fixes as part of 5.5.1 but I also wouldn't want to block a release for non-critical open issues. Both of those issues have no commits and I'm almost done with my back ports. So, unless someone speaks about about actively working on these and makes a case for

RE: Lucene/Solr 5.5.1

Hey Anshum, Can you check if you can take SOLR-9034 for 5.5.1? Will SOLR-8812 make it for 5.5.1? With Thanks & Regards Karthik Ramachandran CommVault P Please don't print this e-mail unless you really need to ***Legal Disclaimer*** "This

Re: Lucene/Solr 5.5.1

Hi Bram, Sure, as long as someone who understands and has access to Windows can take a look at it and commit it. On Wed, Apr 27, 2016 at 12:11 PM, Bram Van Dam wrote: > Hey Anshum, > > Can you have a look at SOLR-9046 as well? It's something that's been > bugging me in

Re: Lucene/Solr 5.5.1

I looked at it Steve but it's unclear in cases of release like this one i.e. 5x release going out when 6.0 is already out. The stable branch as per definition is 6x (and I guess 5x?). On Wed, Apr 27, 2016 at 11:43 AM, Steve Rowe wrote: > Anshum, > > Have you seen >

Re: Lucene/Solr 5.5.1

Hey Anshum, Can you have a look at SOLR-9046 as well? It's something that's been bugging me in 5.5. It's fine if it doesn't make it to 5.5.1, but it would be really nice if it did! Thx, - Bram - To unsubscribe, e-mail:

Re: Lucene/Solr 5.5.1

Anshum, Have you seen https://wiki.apache.org/lucene-java/ReleaseTodo#Update_Version_Numbers_in_the_Source_Code ? -- Steve www.lucidworks.com > On Apr 27, 2016, at 2:33 PM, Anshum Gupta wrote: > > Can someone confirm the steps to update version numbers in source code

Re: Lucene/Solr 5.5.1

Thanks Steve. On Wed, Apr 27, 2016 at 11:38 AM, Steve Rowe wrote: > Hi Anshum, > > Yes, I’ll do the backport now. > > -- > Steve > www.lucidworks.com > > > On Apr 27, 2016, at 2:28 PM, Anshum Gupta > wrote: > > > > Hi Steve, > > > > Yes, I missed the

Re: Lucene/Solr 5.5.1

Hi Anshum, Yes, I’ll do the backport now. -- Steve www.lucidworks.com > On Apr 27, 2016, at 2:28 PM, Anshum Gupta wrote: > > Hi Steve, > > Yes, I missed the JIRA comment. Do you want to take it up? > > On Wed, Apr 27, 2016 at 9:08 AM, Steve Rowe

Re: Lucene/Solr 5.5.1

Can someone confirm the steps to update version numbers in source code for the 5.5.1 release? Here's my understanding: * on branch_5_5: addVersion.py 5.5.1 * Using the commit id from previous step, run addVersion.py on branch_5x * Should we also be running this on master, 6x, and 6.0 branches?

Re: Lucene/Solr 5.5.1

Hi Steve, Yes, I missed the JIRA comment. Do you want to take it up? On Wed, Apr 27, 2016 at 9:08 AM, Steve Rowe wrote: > Anshum, is it okay to backport SOLR-8082 to 5.5.1? - Steve > > > On Apr 27, 2016, at 11:46 AM, Anshum Gupta > wrote: > > > >

Re: Lucene/Solr 5.5.1

Anshum, is it okay to backport SOLR-8082 to 5.5.1? - Steve > On Apr 27, 2016, at 11:46 AM, Anshum Gupta wrote: > > Thanks Yonik. I'll wait for this. > > On Tue, Apr 26, 2016 at 9:42 PM, Yonik Seeley wrote: > On Tue, Apr 26, 2016 at 11:57 PM, Anshum

Re: Lucene/Solr 5.5.1

Thanks Yonik. I'll wait for this. On Tue, Apr 26, 2016 at 9:42 PM, Yonik Seeley wrote: > On Tue, Apr 26, 2016 at 11:57 PM, Anshum Gupta > wrote: > > Hey Tim, Sorry about going slow but there were a ton of back-ports. > > I'm just waiting on Yonik or

Re: Lucene/Solr 5.5.1

no worries, just wanted to get a sense for the timing. Thanks for the update On Tue, Apr 26, 2016 at 9:57 PM, Anshum Gupta wrote: > Hey Tim, Sorry about going slow but there were a ton of back-ports. > I'm just waiting on Yonik or someone else who understands things

Re: Lucene/Solr 5.5.1

On Tue, Apr 26, 2016 at 11:57 PM, Anshum Gupta wrote: > Hey Tim, Sorry about going slow but there were a ton of back-ports. > I'm just waiting on Yonik or someone else who understands things better to > back-port SOLR-8886 Ha, I saw that scroll past. but didn't realize I

Re: Lucene/Solr 5.5.1

Hey Tim, Sorry about going slow but there were a ton of back-ports. I'm just waiting on Yonik or someone else who understands things better to back-port SOLR-8886 and SOLR-8885. I just got done with back-porting everything else earlier today so I'll be ready to spin the RC as soon as those two are

Re: Lucene/Solr 5.5.1

Hi Anshum, What's the status of 5.5.1 RC1? Thanks. On Mon, Apr 18, 2016 at 12:18 PM, Timothy Potter wrote: > it's in, thanks! b3fe7f7..9820406 branch_5_5 -> branch_5_5 > > On Mon, Apr 18, 2016 at 12:06 PM, Anshum Gupta wrote: >> I trust you Tim!

Re: Lucene/Solr 5.5.1

it's in, thanks! b3fe7f7..9820406 branch_5_5 -> branch_5_5 On Mon, Apr 18, 2016 at 12:06 PM, Anshum Gupta wrote: > I trust you Tim! Go for it. > > I wouldn't even commit to review this as there's a lot of stuff on my plate. > > > On Mon, Apr 18, 2016 at 10:31 AM, Timothy

Re: Lucene/Solr 5.5.1

I trust you Tim! Go for it. I wouldn't even commit to review this as there's a lot of stuff on my plate. On Mon, Apr 18, 2016 at 10:31 AM, Timothy Potter wrote: > Hi Anshum, > > I'd like to include the fix for > https://issues.apache.org/jira/browse/SOLR-9007 into 5.5.1.

Re: Lucene/Solr 5.5.1

Hi Anshum, I'd like to include the fix for https://issues.apache.org/jira/browse/SOLR-9007 into 5.5.1. It's super minor (w/ very low risk) and patch is ready. I'd like it to be included because it gives a poor getting started experience if the user selects managed_schema_configs b/c it doesn't

Re: Lucene/Solr 5.5.1

Cassandra, I don't plan on back porting all bug fixes from 6.0 but only the ones that I understand and don't require invasive code changes. I am open to others helping out and back-porting stuff that they understand as long as it's communicated. On Mon, Apr 18, 2016 at 9:47 AM, Cassandra Targett

Re: Lucene/Solr 5.5.1

Anshum, Is your plan to backport all the bug fixes that were released in 6.0 to 5.5.1? Or do you have a selection process you plan to use? Just curious mostly. On Thu, Apr 14, 2016 at 1:44 PM, Timothy Potter wrote: > 8908 is on branch_5_5 now (14ec48a) > > > On Thu, Apr

Re: Lucene/Solr 5.5.1

8908 is on branch_5_5 now (14ec48a) On Thu, Apr 14, 2016 at 9:18 AM, Anshum Gupta wrote: > As Yonik mentioned, I wouldn't be cutting a branch but directly spinning an > RC. I have a few things on my plate so I think I'll only be able to get to > it over the weekend or by

Re: Lucene/Solr 5.5.1

As Yonik mentioned, I wouldn't be cutting a branch but directly spinning an RC. I have a few things on my plate so I think I'll only be able to get to it over the weekend or by Monday, so you still have some time. I wouldn't rush the release specially as this seems like a good candidate for 5.5.1.

Re: Lucene/Solr 5.5.1

If someone else doesn't get to it before I do, I'll do that as part of the 6.0 change log triage/back-port. On Thu, Apr 14, 2016 at 12:59 AM, Bram Van Dam wrote: > On 13/04/16 19:26, Anshum Gupta wrote: > > Can you please test it with 5.5.1 so someone could back port it.

Re: Lucene/Solr 5.5.1

Thanks Tim. I'll take a look. On Wed, Apr 13, 2016 at 7:49 PM, Timothy Potter wrote: > Thanks Anshum. I've pushed a unit test for that ticket ... can you > give it a quick look? > > Cheers, > Tim > > On Wed, Apr 13, 2016 at 11:27 AM, Anshum Gupta >

Re: Lucene/Solr 5.5.1

On Thu, Apr 14, 2016 at 9:36 AM, Noble Paul wrote: > When do you plan to cut a branch, I hope we can include SOLR-8662 into the > release We don't create per-bugfix-release branches. All 5.5.x releases will be made from branch_5_5, which already exists. -Yonik

Re: Lucene/Solr 5.5.1

When do you plan to cut a branch, I hope we can include SOLR-8662 into the release On Thu, Apr 14, 2016 at 1:29 PM, Bram Van Dam wrote: > On 13/04/16 19:26, Anshum Gupta wrote: > > Can you please test it with 5.5.1 so someone could back port it. Thanks. > > I've finished

Re: Lucene/Solr 5.5.1

On 13/04/16 19:26, Anshum Gupta wrote: > Can you please test it with 5.5.1 so someone could back port it. Thanks. I've finished testing SOLR-8145 on branch_5_5. Patch applies cleanly and the bugfix works fine. I don't have commit access, so someone else will have to take care of that part. git

Re: Lucene/Solr 5.5.1

Thanks Anshum. I've pushed a unit test for that ticket ... can you give it a quick look? Cheers, Tim On Wed, Apr 13, 2016 at 11:27 AM, Anshum Gupta wrote: > Go for it Tim! Let us try to get it in with the test and if you need a bit > of time for that, let me know. > > If

Re: Lucene/Solr 5.5.1

Go for it Tim! Let us try to get it in with the test and if you need a bit of time for that, let me know. If you think getting the test would take a lot of time, let us at least get the fix in 5.5.1 if you are confident about the fix. On Wed, Apr 13, 2016 at 9:44 AM, Timothy Potter

Re: Lucene/Solr 5.5.1

Can you please test it with 5.5.1 so someone could back port it. Thanks. On Wed, Apr 13, 2016 at 4:55 AM, Bram Van Dam wrote: > On 11/04/16 19:04, Ishan Chattopadhyaya wrote: > > I'd like someone to backport the following: > > SOLR-8838 > > SOLR-8082 > > SOLR-8865 > > Can

Re: Lucene/Solr 5.5.1

Hi Anshum, I think we should also consider SOLR-8908 for 5.5.1, it's a pretty bad leak esp. in envs that make lots of reloads due to schema edits. I have a fix up, but am struggling to create a test for it atm. Tim On Wed, Apr 13, 2016 at 5:55 AM, Bram Van Dam wrote: > On

Re: Lucene/Solr 5.5.1

On 11/04/16 19:04, Ishan Chattopadhyaya wrote: > I'd like someone to backport the following: > SOLR-8838 > SOLR-8082 > SOLR-8865 Can we please add SOLR-8145 to that list? It fixes an incorrect oom_killer argument in the startupt script and a Jetty warning on startup. Please let me know if you'd

Re: Lucene/Solr 5.5.1

Thanks Ishan. I'll take a look. On Mon, Apr 11, 2016 at 10:04 AM, Ishan Chattopadhyaya < ichattopadhy...@gmail.com> wrote: > Hi Anshum, > > I'd like someone to backport the following: > SOLR-8838 > SOLR-8082 > SOLR-8865 > > These are mentioned in the bug-fix section of 6.0, so I agree with Yonik

Re: Lucene/Solr 5.5.1

I agree and that is on my list of things to do for the release. On Mon, Apr 11, 2016 at 9:25 AM, Yonik Seeley wrote: > On Sun, Apr 10, 2016 at 12:59 PM, Anshum Gupta > wrote: > > Hi, > > > > I would like to release 5.5.1, specially for to SOLR-8725. >

Re: Lucene/Solr 5.5.1

On Mon, Apr 11, 2016 at 2:15 PM Yonik Seeley wrote: > FWIW I backported to the 5x branch (and then to 55 branch from there) > given that we could have a 5.6 release in the future. > Good; I think we should *always* do that when back-porting. Not doing it could really bite us

Re: Lucene/Solr 5.5.1

I just backported SOLR-8155... may do more when I get time, but taxes and other stuff are waiting for me right now. FWIW I backported to the 5x branch (and then to 55 branch from there) given that we could have a 5.6 release in the future. -Yonik On Mon, Apr 11, 2016 at 1:04 PM, Ishan

Re: Lucene/Solr 5.5.1

Hi Anshum, I'd like someone to backport the following: SOLR-8838 SOLR-8082 SOLR-8865 These are mentioned in the bug-fix section of 6.0, so I agree with Yonik that we should perhaps look at all of those changes. Thanks and regards, Ishan On Mon, Apr 11, 2016 at 9:55 PM, Yonik Seeley

Re: Lucene/Solr 5.5.1

On Sun, Apr 10, 2016 at 12:59 PM, Anshum Gupta wrote: > Hi, > > I would like to release 5.5.1, specially for to SOLR-8725. > > SOLR-8642 in 5.5 stops people from upgrading to 5.5 and a lot of users have > spoken about it on the mailing list and the JIRA. > > I would like

Re: Lucene/Solr 5.5.1

FYI I backported https://issues.apache.org/jira/browse/LUCENE-7112 to branch_5_5. Le dim. 10 avr. 2016 à 20:06, Shai Erera a écrit : > +1, this (SOLR-8642) has bitten us already and had to revert back to 5.4.x. > > Shai > > On Sun, Apr 10, 2016 at 8:00 PM Anshum Gupta

Re: Lucene/Solr 5.5.1

+1, this (SOLR-8642) has bitten us already and had to revert back to 5.4.x. Shai On Sun, Apr 10, 2016 at 8:00 PM Anshum Gupta wrote: > Hi, > > I would like to release 5.5.1, specially for to SOLR-8725. > > SOLR-8642 in 5.5 stops people from upgrading to 5.5 and a lot of

Lucene/Solr 5.5.1

Hi, I would like to release 5.5.1, specially for to SOLR-8725. SOLR-8642 in 5.5 stops people from upgrading to 5.5 and a lot of users have spoken about it on the mailing list and the JIRA. I would like to start the process towards the end of the coming week. -- Anshum Gupta