You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Anshum Gupta <an...@anshumgupta.net> on 2015/01/14 03:41:27 UTC
Lucene/Solr 5.0 release branch created
Hi,
I've created the Lucene/Solr release branch for version 5.0:
https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_0
Please only commit important bug fixes to this branch as we're pretty close
to cutting an RC and a release. I don't think I'd be able to do the RC as
planned on Thursday as we still have a blocker issue in SOLR (SOLR-6640).
We should be able to nail that one and get the first RC out early next week.
It's delayed, but it's awesome! :)
--
Anshum Gupta
http://about.me/anshumgupta
Re: Lucene/Solr 5.0 release branch created
Posted by "david.w.smiley@gmail.com" <da...@gmail.com>.
+1 to SOLR-6976 especially.
I’m sad about SpanQueries not getting nuked yet :-(
~ David Smiley
Freelance Apache Lucene/Solr Search Consultant/Developer
http://www.linkedin.com/in/davidwsmiley
Re: Lucene/Solr 5.0 release branch created
Posted by Anshum Gupta <an...@anshumgupta.net>.
Sure Alan, that sounds good to me.
On Wed, Jan 14, 2015 at 6:26 AM, Alan Woodward <al...@flax.co.uk> wrote:
> I'm working through SOLR-6840 (which I think is what Anshum was referring
> to?) at the moment - hopefully I can get this committed today.
>
> Before the release, I'd really like to resolve SOLR-6976 as well, though.
> Leaving deprecated methods in over a major release is asking for trouble
> further down the line!
>
> Alan Woodward
> www.flax.co.uk
>
>
> On 14 Jan 2015, at 14:19, Uwe Schindler wrote:
>
> Hi,
>
> I said yesterday on the corresponding issue that I want to commit
> CustomAnalyzer, so I will do this in a minute.
>
> Uwe
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
> *From:* Anshum Gupta [mailto:anshum@anshumgupta.net]
> *Sent:* Wednesday, January 14, 2015 3:41 AM
> *To:* dev@lucene.apache.org
> *Subject:* Lucene/Solr 5.0 release branch created
>
> Hi,
>
> I've created the Lucene/Solr release branch for version 5.0:
> https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_0
>
> Please only commit important bug fixes to this branch as we're pretty
> close to cutting an RC and a release. I don't think I'd be able to do the
> RC as planned on Thursday as we still have a blocker issue in SOLR
> (SOLR-6640). We should be able to nail that one and get the first RC out
> early next week.
>
> It's delayed, but it's awesome! :)
>
> --
> Anshum Gupta
> http://about.me/anshumgupta
>
>
>
--
Anshum Gupta
http://about.me/anshumgupta
Re: Lucene/Solr 5.0 release branch created
Posted by Alan Woodward <al...@flax.co.uk>.
I'm working through SOLR-6840 (which I think is what Anshum was referring to?) at the moment - hopefully I can get this committed today.
Before the release, I'd really like to resolve SOLR-6976 as well, though. Leaving deprecated methods in over a major release is asking for trouble further down the line!
Alan Woodward
www.flax.co.uk
On 14 Jan 2015, at 14:19, Uwe Schindler wrote:
> Hi,
>
> I said yesterday on the corresponding issue that I want to commit CustomAnalyzer, so I will do this in a minute.
>
> Uwe
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
> From: Anshum Gupta [mailto:anshum@anshumgupta.net]
> Sent: Wednesday, January 14, 2015 3:41 AM
> To: dev@lucene.apache.org
> Subject: Lucene/Solr 5.0 release branch created
>
> Hi,
>
> I've created the Lucene/Solr release branch for version 5.0: https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_0
>
> Please only commit important bug fixes to this branch as we're pretty close to cutting an RC and a release. I don't think I'd be able to do the RC as planned on Thursday as we still have a blocker issue in SOLR (SOLR-6640). We should be able to nail that one and get the first RC out early next week.
>
> It's delayed, but it's awesome! :)
>
> --
> Anshum Gupta
> http://about.me/anshumgupta
RE: Lucene/Solr 5.0 release branch created
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
I said yesterday on the corresponding issue that I want to commit CustomAnalyzer, so I will do this in a minute.
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
<http://www.thetaphi.de/> http://www.thetaphi.de
eMail: uwe@thetaphi.de
From: Anshum Gupta [mailto:anshum@anshumgupta.net]
Sent: Wednesday, January 14, 2015 3:41 AM
To: dev@lucene.apache.org
Subject: Lucene/Solr 5.0 release branch created
Hi,
I've created the Lucene/Solr release branch for version 5.0: https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_0
Please only commit important bug fixes to this branch as we're pretty close to cutting an RC and a release. I don't think I'd be able to do the RC as planned on Thursday as we still have a blocker issue in SOLR (SOLR-6640). We should be able to nail that one and get the first RC out early next week.
It's delayed, but it's awesome! :)
--
Anshum Gupta
http://about.me/anshumgupta
Re: Lucene/Solr 5.0 release branch created
Posted by Anshum Gupta <an...@anshumgupta.net>.
I've added 5.1 for both LUCENE and SOLR.
On Wed, Jan 14, 2015 at 11:49 AM, Anshum Gupta <an...@anshumgupta.net>
wrote:
> Yes, I'll go ahead and do that.
>
> On Wed, Jan 14, 2015 at 10:49 AM, david.w.smiley@gmail.com <
> david.w.smiley@gmail.com> wrote:
>
>> Anshum, are you going to create a 5.1 version in JIRA so we can
>> appropriately assign issues?
>>
>> ~ David Smiley
>> Freelance Apache Lucene/Solr Search Consultant/Developer
>> http://www.linkedin.com/in/davidwsmiley
>>
>> On Wed, Jan 14, 2015 at 12:07 PM, Anshum Gupta <an...@anshumgupta.net>
>> wrote:
>>
>>> Thanks for setting it up.
>>>
>>> On Wed, Jan 14, 2015 at 7:08 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
>>>
>>>> Hi,
>>>>
>>>>
>>>>
>>>> I created a set of Jenkins Jobs:
>>>>
>>>> - Policeman builds 5.0 and runs tests (as usual with all JVMs)
>>>>
>>>> - Apache Jenkins builds Artifacts and Javadocs of Solr and
>>>> Lucene
>>>>
>>>> - Apache Jenkins runs nightly smoker
>>>>
>>>>
>>>>
>>>> -----
>>>>
>>>> Uwe Schindler
>>>>
>>>> H.-H.-Meier-Allee 63, D-28213 Bremen
>>>>
>>>> http://www.thetaphi.de
>>>>
>>>> eMail: uwe@thetaphi.de
>>>>
>>>>
>>>>
>>>> *From:* Anshum Gupta [mailto:anshum@anshumgupta.net]
>>>> *Sent:* Wednesday, January 14, 2015 3:41 AM
>>>> *To:* dev@lucene.apache.org
>>>> *Subject:* Lucene/Solr 5.0 release branch created
>>>>
>>>>
>>>>
>>>> Hi,
>>>>
>>>>
>>>>
>>>> I've created the Lucene/Solr release branch for version 5.0:
>>>> https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_0
>>>>
>>>>
>>>>
>>>> Please only commit important bug fixes to this branch as we're pretty
>>>> close to cutting an RC and a release. I don't think I'd be able to do the
>>>> RC as planned on Thursday as we still have a blocker issue in SOLR
>>>> (SOLR-6640). We should be able to nail that one and get the first RC out
>>>> early next week.
>>>>
>>>>
>>>>
>>>> It's delayed, but it's awesome! :)
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Anshum Gupta
>>>>
>>>> http://about.me/anshumgupta
>>>>
>>>
>>>
>>>
>>> --
>>> Anshum Gupta
>>> http://about.me/anshumgupta
>>>
>>
>>
>
>
> --
> Anshum Gupta
> http://about.me/anshumgupta
>
--
Anshum Gupta
http://about.me/anshumgupta
Re: Lucene/Solr 5.0 release branch created
Posted by Anshum Gupta <an...@anshumgupta.net>.
Yes, I'll go ahead and do that.
On Wed, Jan 14, 2015 at 10:49 AM, david.w.smiley@gmail.com <
david.w.smiley@gmail.com> wrote:
> Anshum, are you going to create a 5.1 version in JIRA so we can
> appropriately assign issues?
>
> ~ David Smiley
> Freelance Apache Lucene/Solr Search Consultant/Developer
> http://www.linkedin.com/in/davidwsmiley
>
> On Wed, Jan 14, 2015 at 12:07 PM, Anshum Gupta <an...@anshumgupta.net>
> wrote:
>
>> Thanks for setting it up.
>>
>> On Wed, Jan 14, 2015 at 7:08 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
>>
>>> Hi,
>>>
>>>
>>>
>>> I created a set of Jenkins Jobs:
>>>
>>> - Policeman builds 5.0 and runs tests (as usual with all JVMs)
>>>
>>> - Apache Jenkins builds Artifacts and Javadocs of Solr and
>>> Lucene
>>>
>>> - Apache Jenkins runs nightly smoker
>>>
>>>
>>>
>>> -----
>>>
>>> Uwe Schindler
>>>
>>> H.-H.-Meier-Allee 63, D-28213 Bremen
>>>
>>> http://www.thetaphi.de
>>>
>>> eMail: uwe@thetaphi.de
>>>
>>>
>>>
>>> *From:* Anshum Gupta [mailto:anshum@anshumgupta.net]
>>> *Sent:* Wednesday, January 14, 2015 3:41 AM
>>> *To:* dev@lucene.apache.org
>>> *Subject:* Lucene/Solr 5.0 release branch created
>>>
>>>
>>>
>>> Hi,
>>>
>>>
>>>
>>> I've created the Lucene/Solr release branch for version 5.0:
>>> https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_0
>>>
>>>
>>>
>>> Please only commit important bug fixes to this branch as we're pretty
>>> close to cutting an RC and a release. I don't think I'd be able to do the
>>> RC as planned on Thursday as we still have a blocker issue in SOLR
>>> (SOLR-6640). We should be able to nail that one and get the first RC out
>>> early next week.
>>>
>>>
>>>
>>> It's delayed, but it's awesome! :)
>>>
>>>
>>>
>>> --
>>>
>>> Anshum Gupta
>>>
>>> http://about.me/anshumgupta
>>>
>>
>>
>>
>> --
>> Anshum Gupta
>> http://about.me/anshumgupta
>>
>
>
--
Anshum Gupta
http://about.me/anshumgupta
Re: Lucene/Solr 5.0 release branch created
Posted by "david.w.smiley@gmail.com" <da...@gmail.com>.
Anshum, are you going to create a 5.1 version in JIRA so we can
appropriately assign issues?
~ David Smiley
Freelance Apache Lucene/Solr Search Consultant/Developer
http://www.linkedin.com/in/davidwsmiley
On Wed, Jan 14, 2015 at 12:07 PM, Anshum Gupta <an...@anshumgupta.net>
wrote:
> Thanks for setting it up.
>
> On Wed, Jan 14, 2015 at 7:08 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
>
>> Hi,
>>
>>
>>
>> I created a set of Jenkins Jobs:
>>
>> - Policeman builds 5.0 and runs tests (as usual with all JVMs)
>>
>> - Apache Jenkins builds Artifacts and Javadocs of Solr and
>> Lucene
>>
>> - Apache Jenkins runs nightly smoker
>>
>>
>>
>> -----
>>
>> Uwe Schindler
>>
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>>
>> http://www.thetaphi.de
>>
>> eMail: uwe@thetaphi.de
>>
>>
>>
>> *From:* Anshum Gupta [mailto:anshum@anshumgupta.net]
>> *Sent:* Wednesday, January 14, 2015 3:41 AM
>> *To:* dev@lucene.apache.org
>> *Subject:* Lucene/Solr 5.0 release branch created
>>
>>
>>
>> Hi,
>>
>>
>>
>> I've created the Lucene/Solr release branch for version 5.0:
>> https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_0
>>
>>
>>
>> Please only commit important bug fixes to this branch as we're pretty
>> close to cutting an RC and a release. I don't think I'd be able to do the
>> RC as planned on Thursday as we still have a blocker issue in SOLR
>> (SOLR-6640). We should be able to nail that one and get the first RC out
>> early next week.
>>
>>
>>
>> It's delayed, but it's awesome! :)
>>
>>
>>
>> --
>>
>> Anshum Gupta
>>
>> http://about.me/anshumgupta
>>
>
>
>
> --
> Anshum Gupta
> http://about.me/anshumgupta
>
Re: Lucene/Solr 5.0 release branch created
Posted by Anshum Gupta <an...@anshumgupta.net>.
Thanks for setting it up.
On Wed, Jan 14, 2015 at 7:08 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
> Hi,
>
>
>
> I created a set of Jenkins Jobs:
>
> - Policeman builds 5.0 and runs tests (as usual with all JVMs)
>
> - Apache Jenkins builds Artifacts and Javadocs of Solr and Lucene
>
> - Apache Jenkins runs nightly smoker
>
>
>
> -----
>
> Uwe Schindler
>
> H.-H.-Meier-Allee 63, D-28213 Bremen
>
> http://www.thetaphi.de
>
> eMail: uwe@thetaphi.de
>
>
>
> *From:* Anshum Gupta [mailto:anshum@anshumgupta.net]
> *Sent:* Wednesday, January 14, 2015 3:41 AM
> *To:* dev@lucene.apache.org
> *Subject:* Lucene/Solr 5.0 release branch created
>
>
>
> Hi,
>
>
>
> I've created the Lucene/Solr release branch for version 5.0:
> https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_0
>
>
>
> Please only commit important bug fixes to this branch as we're pretty
> close to cutting an RC and a release. I don't think I'd be able to do the
> RC as planned on Thursday as we still have a blocker issue in SOLR
> (SOLR-6640). We should be able to nail that one and get the first RC out
> early next week.
>
>
>
> It's delayed, but it's awesome! :)
>
>
>
> --
>
> Anshum Gupta
>
> http://about.me/anshumgupta
>
--
Anshum Gupta
http://about.me/anshumgupta
RE: Lucene/Solr 5.0 release branch created
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
I created a set of Jenkins Jobs:
- Policeman builds 5.0 and runs tests (as usual with all JVMs)
- Apache Jenkins builds Artifacts and Javadocs of Solr and Lucene
- Apache Jenkins runs nightly smoker
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
<http://www.thetaphi.de/> http://www.thetaphi.de
eMail: uwe@thetaphi.de
From: Anshum Gupta [mailto:anshum@anshumgupta.net]
Sent: Wednesday, January 14, 2015 3:41 AM
To: dev@lucene.apache.org
Subject: Lucene/Solr 5.0 release branch created
Hi,
I've created the Lucene/Solr release branch for version 5.0: https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_0
Please only commit important bug fixes to this branch as we're pretty close to cutting an RC and a release. I don't think I'd be able to do the RC as planned on Thursday as we still have a blocker issue in SOLR (SOLR-6640). We should be able to nail that one and get the first RC out early next week.
It's delayed, but it's awesome! :)
--
Anshum Gupta
http://about.me/anshumgupta
Re: Lucene/Solr 5.0 release branch created
Posted by Anshum Gupta <an...@anshumgupta.net>.
I meant that when you build 5x, you'd get 5-1-0-SNAPSHOT.(tgz|zip) and
trunk still gets you a 6.0.0. No existing svn branches have moved/deleted
but just the above mentioned branch was created off 5x for the purpose of
5.0.x releases.
On Tue, Jan 13, 2015 at 6:51 PM, Alexandre Rafalovitch <ar...@gmail.com>
wrote:
> Do you mean, svn_5x is now 5.1? Trunk is 6, right.
>
> Regards,
> Alex.
> ----
> Sign up for my Solr resources newsletter at http://www.solr-start.com/
>
>
> On 13 January 2015 at 21:48, Anshum Gupta <an...@anshumgupta.net> wrote:
> > Also, I forgot to mention, the version# has been bumped on 5x and trunk
> to
> > 5.1.
> >
> > On Tue, Jan 13, 2015 at 6:41 PM, Anshum Gupta <an...@anshumgupta.net>
> > wrote:
> >>
> >> Hi,
> >>
> >> I've created the Lucene/Solr release branch for version 5.0:
> >> https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_0
> >>
> >> Please only commit important bug fixes to this branch as we're pretty
> >> close to cutting an RC and a release. I don't think I'd be able to do
> the RC
> >> as planned on Thursday as we still have a blocker issue in SOLR
> (SOLR-6640).
> >> We should be able to nail that one and get the first RC out early next
> week.
> >>
> >> It's delayed, but it's awesome! :)
> >>
> >> --
> >> Anshum Gupta
> >> http://about.me/anshumgupta
> >
> >
> >
> >
> > --
> > Anshum Gupta
> > http://about.me/anshumgupta
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
--
Anshum Gupta
http://about.me/anshumgupta
Re: Lucene/Solr 5.0 release branch created
Posted by Alexandre Rafalovitch <ar...@gmail.com>.
Do you mean, svn_5x is now 5.1? Trunk is 6, right.
Regards,
Alex.
----
Sign up for my Solr resources newsletter at http://www.solr-start.com/
On 13 January 2015 at 21:48, Anshum Gupta <an...@anshumgupta.net> wrote:
> Also, I forgot to mention, the version# has been bumped on 5x and trunk to
> 5.1.
>
> On Tue, Jan 13, 2015 at 6:41 PM, Anshum Gupta <an...@anshumgupta.net>
> wrote:
>>
>> Hi,
>>
>> I've created the Lucene/Solr release branch for version 5.0:
>> https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_0
>>
>> Please only commit important bug fixes to this branch as we're pretty
>> close to cutting an RC and a release. I don't think I'd be able to do the RC
>> as planned on Thursday as we still have a blocker issue in SOLR (SOLR-6640).
>> We should be able to nail that one and get the first RC out early next week.
>>
>> It's delayed, but it's awesome! :)
>>
>> --
>> Anshum Gupta
>> http://about.me/anshumgupta
>
>
>
>
> --
> Anshum Gupta
> http://about.me/anshumgupta
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Lucene/Solr 5.0 release branch created
Posted by Anshum Gupta <an...@anshumgupta.net>.
Also, I forgot to mention, the version# has been bumped on 5x and trunk to
5.1.
On Tue, Jan 13, 2015 at 6:41 PM, Anshum Gupta <an...@anshumgupta.net>
wrote:
> Hi,
>
> I've created the Lucene/Solr release branch for version 5.0:
> https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_0
>
> Please only commit important bug fixes to this branch as we're pretty
> close to cutting an RC and a release. I don't think I'd be able to do the
> RC as planned on Thursday as we still have a blocker issue in SOLR
> (SOLR-6640). We should be able to nail that one and get the first RC out
> early next week.
>
> It's delayed, but it's awesome! :)
>
> --
> Anshum Gupta
> http://about.me/anshumgupta
>
--
Anshum Gupta
http://about.me/anshumgupta
Re: Lucene/Solr 5.0 release branch created
Posted by Erik Hatcher <er...@gmail.com>.
And FYI, I committed fixes/improvements as part of SOLR-6900 (noted as a “blocker”), which was to a script that is new in 5.0. I’ve also got Solr quick start docs in the works that I’ll commit later today or tomorrow.
Erik
> On Jan 16, 2015, at 2:23 PM, Timothy potter <th...@gmail.com> wrote:
>
> Sorry! Several of the bin/solr changes are mine ... Only critical changes going forward :-)
>
> Sent from my iPhone
>
> On Jan 16, 2015, at 11:18 AM, Anshum Gupta <anshum@anshumgupta.net <ma...@anshumgupta.net>> wrote:
>
>> All of them seem to have come in while I was sleeping! Until last night, it was just the CustomAnalyzer that Uwe had notified about. I certainly don't think SOLR-6937 and SOLR-5147 were fixes for anything but new features.
>>
>> The bin/solr (and example) related changes were fixes that seem to be required for the user to be able to easily use an existing new feature so I'm fine with that but we(the committer) should try and judge before committing those too.
>>
>> Can we stop committing newer stuff? It really wouldn't help with the stability of a major release. I am going to strongly oppose any *new* feature going in now.
>>
>> Also, it'd be good to have more appropriate commit messages that clearly indicate what the commit does. It is generally a good practice but if you want to commit to a release branch, it's almost mandatory.
>>
>>
>>
>>
>> On Fri, Jan 16, 2015 at 5:12 AM, Robert Muir <rcmuir@gmail.com <ma...@gmail.com>> wrote:
>> On Tue, Jan 13, 2015 at 9:41 PM, Anshum Gupta <anshum@anshumgupta.net <ma...@anshumgupta.net>> wrote:
>> >
>> > Please only commit important bug fixes to this branch as we're pretty close
>> > to cutting an RC and a release. I don't think I'd be able to do the RC as
>> > planned on Thursday as we still have a blocker issue in SOLR (SOLR-6640). We
>> > should be able to nail that one and get the first RC out early next week.
>>
>>
>> Why are there an endless flurry of new features to this branch?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
>> For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
>>
>>
>>
>>
>> --
>> Anshum Gupta
>> http://about.me/anshumgupta <http://about.me/anshumgupta>
Re: Lucene/Solr 5.0 release branch created
Posted by Timothy potter <th...@gmail.com>.
Sorry! Several of the bin/solr changes are mine ... Only critical changes going forward :-)
Sent from my iPhone
> On Jan 16, 2015, at 11:18 AM, Anshum Gupta <an...@anshumgupta.net> wrote:
>
> All of them seem to have come in while I was sleeping! Until last night, it was just the CustomAnalyzer that Uwe had notified about. I certainly don't think SOLR-6937 and SOLR-5147 were fixes for anything but new features.
>
> The bin/solr (and example) related changes were fixes that seem to be required for the user to be able to easily use an existing new feature so I'm fine with that but we(the committer) should try and judge before committing those too.
>
> Can we stop committing newer stuff? It really wouldn't help with the stability of a major release. I am going to strongly oppose any *new* feature going in now.
>
> Also, it'd be good to have more appropriate commit messages that clearly indicate what the commit does. It is generally a good practice but if you want to commit to a release branch, it's almost mandatory.
>
>
>
>
>> On Fri, Jan 16, 2015 at 5:12 AM, Robert Muir <rc...@gmail.com> wrote:
>> On Tue, Jan 13, 2015 at 9:41 PM, Anshum Gupta <an...@anshumgupta.net> wrote:
>> >
>> > Please only commit important bug fixes to this branch as we're pretty close
>> > to cutting an RC and a release. I don't think I'd be able to do the RC as
>> > planned on Thursday as we still have a blocker issue in SOLR (SOLR-6640). We
>> > should be able to nail that one and get the first RC out early next week.
>>
>>
>> Why are there an endless flurry of new features to this branch?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
>
> --
> Anshum Gupta
> http://about.me/anshumgupta
Re: Lucene/Solr 5.0 release branch created
Posted by Anshum Gupta <an...@anshumgupta.net>.
SOLR-6937 actually seemed fine as it fixes an issue that users would have
with running 5.0 and that change seems to not impact things.
I'm fine with that one.
On Sat, Jan 17, 2015 at 9:53 AM, Noble Paul <no...@gmail.com> wrote:
> OK I missed the SOLR-6937 part . I can revert that.
>
> On Sat, Jan 17, 2015 at 11:19 PM, Noble Paul <no...@gmail.com> wrote:
>
>> Sorry for the trouble.
>>
>> I committed it because it was a DIH change and not really impacting any
>> of Solr. However , I can roll it back if required
>>
>>
>> On Sat, Jan 17, 2015 at 1:30 AM, Anshum Gupta <an...@anshumgupta.net>
>> wrote:
>>
>>> I think we can have the changes reverted by Noble as he's the original
>>> committer.
>>>
>>> Noble: Can you please revert the new features that you committed onto
>>> the 5.0 branch?
>>>
>>> On Fri, Jan 16, 2015 at 10:42 AM, Michael McCandless <
>>> lucene@mikemccandless.com> wrote:
>>>
>>>> We can just revert the too-dangerous changes? They can wait for 5.1?
>>>>
>>>> Mike McCandless
>>>>
>>>> http://blog.mikemccandless.com
>>>>
>>>>
>>>> On Fri, Jan 16, 2015 at 1:18 PM, Anshum Gupta <an...@anshumgupta.net>
>>>> wrote:
>>>> > All of them seem to have come in while I was sleeping! Until last
>>>> night, it
>>>> > was just the CustomAnalyzer that Uwe had notified about. I certainly
>>>> don't
>>>> > think SOLR-6937 and SOLR-5147 were fixes for anything but new
>>>> features.
>>>> >
>>>> > The bin/solr (and example) related changes were fixes that seem to be
>>>> > required for the user to be able to easily use an existing new
>>>> feature so
>>>> > I'm fine with that but we(the committer) should try and judge before
>>>> > committing those too.
>>>> >
>>>> > Can we stop committing newer stuff? It really wouldn't help with the
>>>> > stability of a major release. I am going to strongly oppose any *new*
>>>> > feature going in now.
>>>> >
>>>> > Also, it'd be good to have more appropriate commit messages that
>>>> clearly
>>>> > indicate what the commit does. It is generally a good practice but if
>>>> you
>>>> > want to commit to a release branch, it's almost mandatory.
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > On Fri, Jan 16, 2015 at 5:12 AM, Robert Muir <rc...@gmail.com>
>>>> wrote:
>>>> >>
>>>> >> On Tue, Jan 13, 2015 at 9:41 PM, Anshum Gupta <
>>>> anshum@anshumgupta.net>
>>>> >> wrote:
>>>> >> >
>>>> >> > Please only commit important bug fixes to this branch as we're
>>>> pretty
>>>> >> > close
>>>> >> > to cutting an RC and a release. I don't think I'd be able to do
>>>> the RC
>>>> >> > as
>>>> >> > planned on Thursday as we still have a blocker issue in SOLR
>>>> >> > (SOLR-6640). We
>>>> >> > should be able to nail that one and get the first RC out early next
>>>> >> > week.
>>>> >>
>>>> >>
>>>> >> Why are there an endless flurry of new features to this branch?
>>>> >>
>>>> >> ---------------------------------------------------------------------
>>>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Anshum Gupta
>>>> > http://about.me/anshumgupta
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Anshum Gupta
>>> http://about.me/anshumgupta
>>>
>>
>>
>>
>> --
>> -----------------------------------------------------
>> Noble Paul
>>
>
>
>
> --
> -----------------------------------------------------
> Noble Paul
>
--
Anshum Gupta
http://about.me/anshumgupta
Re: Lucene/Solr 5.0 release branch created
Posted by Alexandre Rafalovitch <ar...@gmail.com>.
Could we make sure to fix SOLR-6960, please! Otherwise, Solr is
basically lying about its configuration OOTB.
Regards,
Alex.
----
Sign up for my Solr resources newsletter at http://www.solr-start.com/
On 17 January 2015 at 13:36, Anshum Gupta <an...@anshumgupta.net> wrote:
> Thanks Noble. I'm just trying to minimize adding more variables to the
> release branch.
>
> On Sat, Jan 17, 2015 at 10:27 AM, Noble Paul <no...@gmail.com> wrote:
>>
>> Both are reverted
>>
>> On Sat, Jan 17, 2015 at 11:23 PM, Noble Paul <no...@gmail.com> wrote:
>>>
>>> OK I missed the SOLR-6937 part . I can revert that.
>>>
>>> On Sat, Jan 17, 2015 at 11:19 PM, Noble Paul <no...@gmail.com>
>>> wrote:
>>>>
>>>> Sorry for the trouble.
>>>>
>>>> I committed it because it was a DIH change and not really impacting any
>>>> of Solr. However , I can roll it back if required
>>>>
>>>>
>>>> On Sat, Jan 17, 2015 at 1:30 AM, Anshum Gupta <an...@anshumgupta.net>
>>>> wrote:
>>>>>
>>>>> I think we can have the changes reverted by Noble as he's the original
>>>>> committer.
>>>>>
>>>>> Noble: Can you please revert the new features that you committed onto
>>>>> the 5.0 branch?
>>>>>
>>>>> On Fri, Jan 16, 2015 at 10:42 AM, Michael McCandless
>>>>> <lu...@mikemccandless.com> wrote:
>>>>>>
>>>>>> We can just revert the too-dangerous changes? They can wait for 5.1?
>>>>>>
>>>>>> Mike McCandless
>>>>>>
>>>>>> http://blog.mikemccandless.com
>>>>>>
>>>>>>
>>>>>> On Fri, Jan 16, 2015 at 1:18 PM, Anshum Gupta <an...@anshumgupta.net>
>>>>>> wrote:
>>>>>> > All of them seem to have come in while I was sleeping! Until last
>>>>>> > night, it
>>>>>> > was just the CustomAnalyzer that Uwe had notified about. I certainly
>>>>>> > don't
>>>>>> > think SOLR-6937 and SOLR-5147 were fixes for anything but new
>>>>>> > features.
>>>>>> >
>>>>>> > The bin/solr (and example) related changes were fixes that seem to
>>>>>> > be
>>>>>> > required for the user to be able to easily use an existing new
>>>>>> > feature so
>>>>>> > I'm fine with that but we(the committer) should try and judge before
>>>>>> > committing those too.
>>>>>> >
>>>>>> > Can we stop committing newer stuff? It really wouldn't help with the
>>>>>> > stability of a major release. I am going to strongly oppose any
>>>>>> > *new*
>>>>>> > feature going in now.
>>>>>> >
>>>>>> > Also, it'd be good to have more appropriate commit messages that
>>>>>> > clearly
>>>>>> > indicate what the commit does. It is generally a good practice but
>>>>>> > if you
>>>>>> > want to commit to a release branch, it's almost mandatory.
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > On Fri, Jan 16, 2015 at 5:12 AM, Robert Muir <rc...@gmail.com>
>>>>>> > wrote:
>>>>>> >>
>>>>>> >> On Tue, Jan 13, 2015 at 9:41 PM, Anshum Gupta
>>>>>> >> <an...@anshumgupta.net>
>>>>>> >> wrote:
>>>>>> >> >
>>>>>> >> > Please only commit important bug fixes to this branch as we're
>>>>>> >> > pretty
>>>>>> >> > close
>>>>>> >> > to cutting an RC and a release. I don't think I'd be able to do
>>>>>> >> > the RC
>>>>>> >> > as
>>>>>> >> > planned on Thursday as we still have a blocker issue in SOLR
>>>>>> >> > (SOLR-6640). We
>>>>>> >> > should be able to nail that one and get the first RC out early
>>>>>> >> > next
>>>>>> >> > week.
>>>>>> >>
>>>>>> >>
>>>>>> >> Why are there an endless flurry of new features to this branch?
>>>>>> >>
>>>>>> >>
>>>>>> >> ---------------------------------------------------------------------
>>>>>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>> >>
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > --
>>>>>> > Anshum Gupta
>>>>>> > http://about.me/anshumgupta
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Anshum Gupta
>>>>> http://about.me/anshumgupta
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> -----------------------------------------------------
>>>> Noble Paul
>>>
>>>
>>>
>>>
>>> --
>>> -----------------------------------------------------
>>> Noble Paul
>>
>>
>>
>>
>> --
>> -----------------------------------------------------
>> Noble Paul
>
>
>
>
> --
> Anshum Gupta
> http://about.me/anshumgupta
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Lucene/Solr 5.0 release branch created
Posted by Anshum Gupta <an...@anshumgupta.net>.
Thanks Noble. I'm just trying to minimize adding more variables to the
release branch.
On Sat, Jan 17, 2015 at 10:27 AM, Noble Paul <no...@gmail.com> wrote:
> Both are reverted
>
> On Sat, Jan 17, 2015 at 11:23 PM, Noble Paul <no...@gmail.com> wrote:
>
>> OK I missed the SOLR-6937 part . I can revert that.
>>
>> On Sat, Jan 17, 2015 at 11:19 PM, Noble Paul <no...@gmail.com>
>> wrote:
>>
>>> Sorry for the trouble.
>>>
>>> I committed it because it was a DIH change and not really impacting any
>>> of Solr. However , I can roll it back if required
>>>
>>>
>>> On Sat, Jan 17, 2015 at 1:30 AM, Anshum Gupta <an...@anshumgupta.net>
>>> wrote:
>>>
>>>> I think we can have the changes reverted by Noble as he's the original
>>>> committer.
>>>>
>>>> Noble: Can you please revert the new features that you committed onto
>>>> the 5.0 branch?
>>>>
>>>> On Fri, Jan 16, 2015 at 10:42 AM, Michael McCandless <
>>>> lucene@mikemccandless.com> wrote:
>>>>
>>>>> We can just revert the too-dangerous changes? They can wait for 5.1?
>>>>>
>>>>> Mike McCandless
>>>>>
>>>>> http://blog.mikemccandless.com
>>>>>
>>>>>
>>>>> On Fri, Jan 16, 2015 at 1:18 PM, Anshum Gupta <an...@anshumgupta.net>
>>>>> wrote:
>>>>> > All of them seem to have come in while I was sleeping! Until last
>>>>> night, it
>>>>> > was just the CustomAnalyzer that Uwe had notified about. I certainly
>>>>> don't
>>>>> > think SOLR-6937 and SOLR-5147 were fixes for anything but new
>>>>> features.
>>>>> >
>>>>> > The bin/solr (and example) related changes were fixes that seem to be
>>>>> > required for the user to be able to easily use an existing new
>>>>> feature so
>>>>> > I'm fine with that but we(the committer) should try and judge before
>>>>> > committing those too.
>>>>> >
>>>>> > Can we stop committing newer stuff? It really wouldn't help with the
>>>>> > stability of a major release. I am going to strongly oppose any *new*
>>>>> > feature going in now.
>>>>> >
>>>>> > Also, it'd be good to have more appropriate commit messages that
>>>>> clearly
>>>>> > indicate what the commit does. It is generally a good practice but
>>>>> if you
>>>>> > want to commit to a release branch, it's almost mandatory.
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > On Fri, Jan 16, 2015 at 5:12 AM, Robert Muir <rc...@gmail.com>
>>>>> wrote:
>>>>> >>
>>>>> >> On Tue, Jan 13, 2015 at 9:41 PM, Anshum Gupta <
>>>>> anshum@anshumgupta.net>
>>>>> >> wrote:
>>>>> >> >
>>>>> >> > Please only commit important bug fixes to this branch as we're
>>>>> pretty
>>>>> >> > close
>>>>> >> > to cutting an RC and a release. I don't think I'd be able to do
>>>>> the RC
>>>>> >> > as
>>>>> >> > planned on Thursday as we still have a blocker issue in SOLR
>>>>> >> > (SOLR-6640). We
>>>>> >> > should be able to nail that one and get the first RC out early
>>>>> next
>>>>> >> > week.
>>>>> >>
>>>>> >>
>>>>> >> Why are there an endless flurry of new features to this branch?
>>>>> >>
>>>>> >>
>>>>> ---------------------------------------------------------------------
>>>>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>> >>
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > Anshum Gupta
>>>>> > http://about.me/anshumgupta
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Anshum Gupta
>>>> http://about.me/anshumgupta
>>>>
>>>
>>>
>>>
>>> --
>>> -----------------------------------------------------
>>> Noble Paul
>>>
>>
>>
>>
>> --
>> -----------------------------------------------------
>> Noble Paul
>>
>
>
>
> --
> -----------------------------------------------------
> Noble Paul
>
--
Anshum Gupta
http://about.me/anshumgupta
Re: Lucene/Solr 5.0 release branch created
Posted by Noble Paul <no...@gmail.com>.
Both are reverted
On Sat, Jan 17, 2015 at 11:23 PM, Noble Paul <no...@gmail.com> wrote:
> OK I missed the SOLR-6937 part . I can revert that.
>
> On Sat, Jan 17, 2015 at 11:19 PM, Noble Paul <no...@gmail.com> wrote:
>
>> Sorry for the trouble.
>>
>> I committed it because it was a DIH change and not really impacting any
>> of Solr. However , I can roll it back if required
>>
>>
>> On Sat, Jan 17, 2015 at 1:30 AM, Anshum Gupta <an...@anshumgupta.net>
>> wrote:
>>
>>> I think we can have the changes reverted by Noble as he's the original
>>> committer.
>>>
>>> Noble: Can you please revert the new features that you committed onto
>>> the 5.0 branch?
>>>
>>> On Fri, Jan 16, 2015 at 10:42 AM, Michael McCandless <
>>> lucene@mikemccandless.com> wrote:
>>>
>>>> We can just revert the too-dangerous changes? They can wait for 5.1?
>>>>
>>>> Mike McCandless
>>>>
>>>> http://blog.mikemccandless.com
>>>>
>>>>
>>>> On Fri, Jan 16, 2015 at 1:18 PM, Anshum Gupta <an...@anshumgupta.net>
>>>> wrote:
>>>> > All of them seem to have come in while I was sleeping! Until last
>>>> night, it
>>>> > was just the CustomAnalyzer that Uwe had notified about. I certainly
>>>> don't
>>>> > think SOLR-6937 and SOLR-5147 were fixes for anything but new
>>>> features.
>>>> >
>>>> > The bin/solr (and example) related changes were fixes that seem to be
>>>> > required for the user to be able to easily use an existing new
>>>> feature so
>>>> > I'm fine with that but we(the committer) should try and judge before
>>>> > committing those too.
>>>> >
>>>> > Can we stop committing newer stuff? It really wouldn't help with the
>>>> > stability of a major release. I am going to strongly oppose any *new*
>>>> > feature going in now.
>>>> >
>>>> > Also, it'd be good to have more appropriate commit messages that
>>>> clearly
>>>> > indicate what the commit does. It is generally a good practice but if
>>>> you
>>>> > want to commit to a release branch, it's almost mandatory.
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > On Fri, Jan 16, 2015 at 5:12 AM, Robert Muir <rc...@gmail.com>
>>>> wrote:
>>>> >>
>>>> >> On Tue, Jan 13, 2015 at 9:41 PM, Anshum Gupta <
>>>> anshum@anshumgupta.net>
>>>> >> wrote:
>>>> >> >
>>>> >> > Please only commit important bug fixes to this branch as we're
>>>> pretty
>>>> >> > close
>>>> >> > to cutting an RC and a release. I don't think I'd be able to do
>>>> the RC
>>>> >> > as
>>>> >> > planned on Thursday as we still have a blocker issue in SOLR
>>>> >> > (SOLR-6640). We
>>>> >> > should be able to nail that one and get the first RC out early next
>>>> >> > week.
>>>> >>
>>>> >>
>>>> >> Why are there an endless flurry of new features to this branch?
>>>> >>
>>>> >> ---------------------------------------------------------------------
>>>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Anshum Gupta
>>>> > http://about.me/anshumgupta
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Anshum Gupta
>>> http://about.me/anshumgupta
>>>
>>
>>
>>
>> --
>> -----------------------------------------------------
>> Noble Paul
>>
>
>
>
> --
> -----------------------------------------------------
> Noble Paul
>
--
-----------------------------------------------------
Noble Paul
Re: Lucene/Solr 5.0 release branch created
Posted by Noble Paul <no...@gmail.com>.
OK I missed the SOLR-6937 part . I can revert that.
On Sat, Jan 17, 2015 at 11:19 PM, Noble Paul <no...@gmail.com> wrote:
> Sorry for the trouble.
>
> I committed it because it was a DIH change and not really impacting any of
> Solr. However , I can roll it back if required
>
>
> On Sat, Jan 17, 2015 at 1:30 AM, Anshum Gupta <an...@anshumgupta.net>
> wrote:
>
>> I think we can have the changes reverted by Noble as he's the original
>> committer.
>>
>> Noble: Can you please revert the new features that you committed onto the
>> 5.0 branch?
>>
>> On Fri, Jan 16, 2015 at 10:42 AM, Michael McCandless <
>> lucene@mikemccandless.com> wrote:
>>
>>> We can just revert the too-dangerous changes? They can wait for 5.1?
>>>
>>> Mike McCandless
>>>
>>> http://blog.mikemccandless.com
>>>
>>>
>>> On Fri, Jan 16, 2015 at 1:18 PM, Anshum Gupta <an...@anshumgupta.net>
>>> wrote:
>>> > All of them seem to have come in while I was sleeping! Until last
>>> night, it
>>> > was just the CustomAnalyzer that Uwe had notified about. I certainly
>>> don't
>>> > think SOLR-6937 and SOLR-5147 were fixes for anything but new
>>> features.
>>> >
>>> > The bin/solr (and example) related changes were fixes that seem to be
>>> > required for the user to be able to easily use an existing new feature
>>> so
>>> > I'm fine with that but we(the committer) should try and judge before
>>> > committing those too.
>>> >
>>> > Can we stop committing newer stuff? It really wouldn't help with the
>>> > stability of a major release. I am going to strongly oppose any *new*
>>> > feature going in now.
>>> >
>>> > Also, it'd be good to have more appropriate commit messages that
>>> clearly
>>> > indicate what the commit does. It is generally a good practice but if
>>> you
>>> > want to commit to a release branch, it's almost mandatory.
>>> >
>>> >
>>> >
>>> >
>>> > On Fri, Jan 16, 2015 at 5:12 AM, Robert Muir <rc...@gmail.com> wrote:
>>> >>
>>> >> On Tue, Jan 13, 2015 at 9:41 PM, Anshum Gupta <anshum@anshumgupta.net
>>> >
>>> >> wrote:
>>> >> >
>>> >> > Please only commit important bug fixes to this branch as we're
>>> pretty
>>> >> > close
>>> >> > to cutting an RC and a release. I don't think I'd be able to do the
>>> RC
>>> >> > as
>>> >> > planned on Thursday as we still have a blocker issue in SOLR
>>> >> > (SOLR-6640). We
>>> >> > should be able to nail that one and get the first RC out early next
>>> >> > week.
>>> >>
>>> >>
>>> >> Why are there an endless flurry of new features to this branch?
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Anshum Gupta
>>> > http://about.me/anshumgupta
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>>
>>
>>
>> --
>> Anshum Gupta
>> http://about.me/anshumgupta
>>
>
>
>
> --
> -----------------------------------------------------
> Noble Paul
>
--
-----------------------------------------------------
Noble Paul
Re: Lucene/Solr 5.0 release branch created
Posted by Noble Paul <no...@gmail.com>.
Sorry for the trouble.
I committed it because it was a DIH change and not really impacting any of
Solr. However , I can roll it back if required
On Sat, Jan 17, 2015 at 1:30 AM, Anshum Gupta <an...@anshumgupta.net>
wrote:
> I think we can have the changes reverted by Noble as he's the original
> committer.
>
> Noble: Can you please revert the new features that you committed onto the
> 5.0 branch?
>
> On Fri, Jan 16, 2015 at 10:42 AM, Michael McCandless <
> lucene@mikemccandless.com> wrote:
>
>> We can just revert the too-dangerous changes? They can wait for 5.1?
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>>
>> On Fri, Jan 16, 2015 at 1:18 PM, Anshum Gupta <an...@anshumgupta.net>
>> wrote:
>> > All of them seem to have come in while I was sleeping! Until last
>> night, it
>> > was just the CustomAnalyzer that Uwe had notified about. I certainly
>> don't
>> > think SOLR-6937 and SOLR-5147 were fixes for anything but new features.
>> >
>> > The bin/solr (and example) related changes were fixes that seem to be
>> > required for the user to be able to easily use an existing new feature
>> so
>> > I'm fine with that but we(the committer) should try and judge before
>> > committing those too.
>> >
>> > Can we stop committing newer stuff? It really wouldn't help with the
>> > stability of a major release. I am going to strongly oppose any *new*
>> > feature going in now.
>> >
>> > Also, it'd be good to have more appropriate commit messages that clearly
>> > indicate what the commit does. It is generally a good practice but if
>> you
>> > want to commit to a release branch, it's almost mandatory.
>> >
>> >
>> >
>> >
>> > On Fri, Jan 16, 2015 at 5:12 AM, Robert Muir <rc...@gmail.com> wrote:
>> >>
>> >> On Tue, Jan 13, 2015 at 9:41 PM, Anshum Gupta <an...@anshumgupta.net>
>> >> wrote:
>> >> >
>> >> > Please only commit important bug fixes to this branch as we're pretty
>> >> > close
>> >> > to cutting an RC and a release. I don't think I'd be able to do the
>> RC
>> >> > as
>> >> > planned on Thursday as we still have a blocker issue in SOLR
>> >> > (SOLR-6640). We
>> >> > should be able to nail that one and get the first RC out early next
>> >> > week.
>> >>
>> >>
>> >> Why are there an endless flurry of new features to this branch?
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>
>> >
>> >
>> >
>> > --
>> > Anshum Gupta
>> > http://about.me/anshumgupta
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
>
> --
> Anshum Gupta
> http://about.me/anshumgupta
>
--
-----------------------------------------------------
Noble Paul
Re: Lucene/Solr 5.0 release branch created
Posted by Anshum Gupta <an...@anshumgupta.net>.
I think we can have the changes reverted by Noble as he's the original
committer.
Noble: Can you please revert the new features that you committed onto the
5.0 branch?
On Fri, Jan 16, 2015 at 10:42 AM, Michael McCandless <
lucene@mikemccandless.com> wrote:
> We can just revert the too-dangerous changes? They can wait for 5.1?
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Fri, Jan 16, 2015 at 1:18 PM, Anshum Gupta <an...@anshumgupta.net>
> wrote:
> > All of them seem to have come in while I was sleeping! Until last night,
> it
> > was just the CustomAnalyzer that Uwe had notified about. I certainly
> don't
> > think SOLR-6937 and SOLR-5147 were fixes for anything but new features.
> >
> > The bin/solr (and example) related changes were fixes that seem to be
> > required for the user to be able to easily use an existing new feature so
> > I'm fine with that but we(the committer) should try and judge before
> > committing those too.
> >
> > Can we stop committing newer stuff? It really wouldn't help with the
> > stability of a major release. I am going to strongly oppose any *new*
> > feature going in now.
> >
> > Also, it'd be good to have more appropriate commit messages that clearly
> > indicate what the commit does. It is generally a good practice but if you
> > want to commit to a release branch, it's almost mandatory.
> >
> >
> >
> >
> > On Fri, Jan 16, 2015 at 5:12 AM, Robert Muir <rc...@gmail.com> wrote:
> >>
> >> On Tue, Jan 13, 2015 at 9:41 PM, Anshum Gupta <an...@anshumgupta.net>
> >> wrote:
> >> >
> >> > Please only commit important bug fixes to this branch as we're pretty
> >> > close
> >> > to cutting an RC and a release. I don't think I'd be able to do the RC
> >> > as
> >> > planned on Thursday as we still have a blocker issue in SOLR
> >> > (SOLR-6640). We
> >> > should be able to nail that one and get the first RC out early next
> >> > week.
> >>
> >>
> >> Why are there an endless flurry of new features to this branch?
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: dev-help@lucene.apache.org
> >>
> >
> >
> >
> > --
> > Anshum Gupta
> > http://about.me/anshumgupta
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
--
Anshum Gupta
http://about.me/anshumgupta
Re: Lucene/Solr 5.0 release branch created
Posted by Michael McCandless <lu...@mikemccandless.com>.
We can just revert the too-dangerous changes? They can wait for 5.1?
Mike McCandless
http://blog.mikemccandless.com
On Fri, Jan 16, 2015 at 1:18 PM, Anshum Gupta <an...@anshumgupta.net> wrote:
> All of them seem to have come in while I was sleeping! Until last night, it
> was just the CustomAnalyzer that Uwe had notified about. I certainly don't
> think SOLR-6937 and SOLR-5147 were fixes for anything but new features.
>
> The bin/solr (and example) related changes were fixes that seem to be
> required for the user to be able to easily use an existing new feature so
> I'm fine with that but we(the committer) should try and judge before
> committing those too.
>
> Can we stop committing newer stuff? It really wouldn't help with the
> stability of a major release. I am going to strongly oppose any *new*
> feature going in now.
>
> Also, it'd be good to have more appropriate commit messages that clearly
> indicate what the commit does. It is generally a good practice but if you
> want to commit to a release branch, it's almost mandatory.
>
>
>
>
> On Fri, Jan 16, 2015 at 5:12 AM, Robert Muir <rc...@gmail.com> wrote:
>>
>> On Tue, Jan 13, 2015 at 9:41 PM, Anshum Gupta <an...@anshumgupta.net>
>> wrote:
>> >
>> > Please only commit important bug fixes to this branch as we're pretty
>> > close
>> > to cutting an RC and a release. I don't think I'd be able to do the RC
>> > as
>> > planned on Thursday as we still have a blocker issue in SOLR
>> > (SOLR-6640). We
>> > should be able to nail that one and get the first RC out early next
>> > week.
>>
>>
>> Why are there an endless flurry of new features to this branch?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
>
>
> --
> Anshum Gupta
> http://about.me/anshumgupta
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Lucene/Solr 5.0 release branch created
Posted by Anshum Gupta <an...@anshumgupta.net>.
All of them seem to have come in while I was sleeping! Until last night, it
was just the CustomAnalyzer that Uwe had notified about. I certainly don't
think SOLR-6937 and SOLR-5147 were fixes for anything but new features.
The bin/solr (and example) related changes were fixes that seem to be
required for the user to be able to easily use an existing new feature so
I'm fine with that but we(the committer) should try and judge before
committing those too.
Can we stop committing newer stuff? It really wouldn't help with the
stability of a major release. I am going to strongly oppose any *new*
feature going in now.
Also, it'd be good to have more appropriate commit messages that clearly
indicate what the commit does. It is generally a good practice but if you
want to commit to a release branch, it's almost mandatory.
On Fri, Jan 16, 2015 at 5:12 AM, Robert Muir <rc...@gmail.com> wrote:
> On Tue, Jan 13, 2015 at 9:41 PM, Anshum Gupta <an...@anshumgupta.net>
> wrote:
> >
> > Please only commit important bug fixes to this branch as we're pretty
> close
> > to cutting an RC and a release. I don't think I'd be able to do the RC as
> > planned on Thursday as we still have a blocker issue in SOLR
> (SOLR-6640). We
> > should be able to nail that one and get the first RC out early next week.
>
>
> Why are there an endless flurry of new features to this branch?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
--
Anshum Gupta
http://about.me/anshumgupta
Re: Lucene/Solr 5.0 release branch created
Posted by Robert Muir <rc...@gmail.com>.
On Tue, Jan 13, 2015 at 9:41 PM, Anshum Gupta <an...@anshumgupta.net> wrote:
>
> Please only commit important bug fixes to this branch as we're pretty close
> to cutting an RC and a release. I don't think I'd be able to do the RC as
> planned on Thursday as we still have a blocker issue in SOLR (SOLR-6640). We
> should be able to nail that one and get the first RC out early next week.
Why are there an endless flurry of new features to this branch?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org