I think those would be risky to backport, there was a lot of
refactoring and cleanup across many issues. Some of the fixes relied
on fixing the encoding and things like that.

On Fri, May 20, 2016 at 2:53 PM, Steve Rowe <[email protected]> wrote:
> Thanks Mike, sounds good.
>
> BTW, (CC’ing Robert too), I tried to backport the following 6.1 bugfixes, but 
> cherry-picking the branch_6x commits into branch_6_0 wasn’t clean ("both 
> modified” for several files for each issue) - do you think they’re 
> worthy/capable of being backported?:
>
> * LUCENE-7127: Fix corner case bugs in GeoPointDistanceQuery. (Robert Muir)
>
> * LUCENE-7166: Fix corner case bugs in LatLonPoint/GeoPointField bounding box
>   queries. (Robert Muir)
>
> * LUCENE-7168: Switch to stable encode for geo3d, remove quantization
>   test leniency, remove dead code (Mike McCandless)
>
> --
> Steve
> www.lucidworks.com
>
>> On May 20, 2016, at 2:36 PM, Michael McCandless <[email protected]> 
>> wrote:
>>
>> Hi Steve,
>>
>> I think we should also fix https://issues.apache.org/jira/browse/LUCENE-7293 
>> for 6.0.1 ... I'll commit shortly.
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>> On Sun, May 15, 2016 at 12:20 AM, Steve Rowe <[email protected]> wrote:
>> Yes, I will fix up trunk and branch_6x CHANGES.txt for backported issues.
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>> > On May 14, 2016, at 12:33 AM, David Smiley <[email protected]> 
>> > wrote:
>> >
>> > Oh right, of course :-)  So I cherry picked those over to the 6.0 branch.  
>> > The Lucene one is strictly speaking a "new feature" but it's to make the 
>> > GCD configurable necessary to enable the Solr-side to use it without a 
>> > GCD.  At some point after the release I presume you'll sync up the 
>> > CHANGES.txt on master & 6x?  That'd be easier than trying to make that 
>> > change for each cherry picked commit.  It's too bad this 
>> > conundrum/annoyance exists.
>> >
>> > ~ David
>> >
>> > On Fri, May 13, 2016 at 8:11 PM Steve Rowe <[email protected]> wrote:
>> > David,
>> >
>> > Since it’s a bugfix release, the branch is already cut: branch_6_0.
>> >
>> > Please go ahead and start backporting whenever you’re ready.
>> >
>> > --
>> > Steve
>> > www.lucidworks.com
>> >
>> > > On May 13, 2016, at 12:24 PM, David Smiley <[email protected]> 
>> > > wrote:
>> > >
>> > > When you cut the branch, I'll port the "gregorian change date" 
>> > > bugs/issues (2 Solr, 1 Lucene).
>> > >
>> > > On Fri, May 13, 2016 at 12:06 PM Steve Rowe <[email protected]> wrote:
>> > > I’d like to make a 6.0.1 release, and I volunteer to be RM.
>> > >
>> > > I propose to cut the first RC in one week: next Friday.
>> > >
>> > > --
>> > > Steve
>> > > www.lucidworks.com
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: [email protected]
>> > > For additional commands, e-mail: [email protected]
>> > >
>> > > --
>> > > Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
>> > > LinkedIn: http://linkedin.com/in/davidwsmiley | Book: 
>> > > http://www.solrenterprisesearchserver.com
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [email protected]
>> > For additional commands, e-mail: [email protected]
>> >
>> > --
>> > Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
>> > LinkedIn: http://linkedin.com/in/davidwsmiley | Book: 
>> > http://www.solrenterprisesearchserver.com
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to