I'd like to see https://issues.apache.org/
jira/browse/SOLR-10985included in 7.0 since it's a small low-risk change but it being in cache classes will benefit many users.ChristineFrom: firstname.lastname@example.org At: 07/05/17 16:00:48To: email@example.com
Subject: Re: Feature freeze @ 7.0 branchSure Mikhail, and Mike.-AnshumOn Jul 5, 2017, at 5:09 AM, Mikhail Khludnev <firstname.lastname@example.org> wrote:Is it worth to push https://issues.apache.
org/jira/browse/SOLR-10986fixes regression in https://issues.apache.org/ jira/browse/SOLR-6357into 7.0?On Wed, Jul 5, 2017 at 12:48 PM, Michael McCandless <email@example.com> wrote:Hi Anshum, I'd like to do https://issues.apache.org/ jira/browse/LUCENE-7899for 7.0; it's a simple rename, which I think we should do on major release. I'll get a patch up shortly.Thanks,On Tue, Jul 4, 2017 at 12:40 PM, Anshum Gupta <firstname.lastname@example.org> wrote:Sure Ab, this is an important bug fix.-AnshumOn 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 <email@example.com> wrote:Hi,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.-Anshum--Sincerely yours