I was hoping to get https://issues.apache.org/jira/browse/SOLR-9526 in 7.0 to go along with the improved usability of data driven schema. Still one NOCOMMIT to solve. WDYT?

Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com

5. jul. 2017 kl. 14.09 skrev Mikhail Khludnev <mkhl@apache.org>:

Is it worth to push https://issues.apache.org/jira/browse/SOLR-10986 fixes regression in https://issues.apache.org/jira/browse/SOLR-6357 into 7.0?  

On Wed, Jul 5, 2017 at 12:48 PM, Michael McCandless <lucene@mikemccandless.com> wrote:
Hi Anshum, I'd like to do https://issues.apache.org/jira/browse/LUCENE-7899 for 7.0; it's a simple rename, which I think we should do on major release.  I'll get a patch up shortly.


On Tue, Jul 4, 2017 at 12:40 PM, Anshum Gupta <anshum@anshumgupta.net> wrote:
Sure Ab, this is an important bug fix.


On Tue, Jul 4, 2017 at 9:35 AM Andrzej Białecki <andrzej.bialecki@lucidworks.com> wrote:
SOLR-10878 and SOLR-10879 didn’t make it before the branches were cut, but I think they should be included in 7x and 7_0 - I’m going to cherry-pick the commits from master.

On 3 Jul 2017, at 22:29, Anshum Gupta <anshumg@apple.com> wrote:


I just wanted to call it out and remove any confusions around the fact that we shouldn’t we committing ‘new features’ to branch_7_0. As far as whatever was already agreed upon in previous communications, let’s get that stuff in if it’s ready or almost there. For everything else, kindly check before you commit to the release branch.

Let us make sure that the bugs and edge cases are all taken care of, the deprecations, and cleanups too.

P.S: Feel free to commit bug fixes without checking, but make sure that we aren’t hiding features in those commits.


Sincerely yours
Mikhail Khludnev