I meant ‘re-spin’. :)
-Anshum
> On Aug 29, 2017, at 2:23 PM, Anshum Gupta wrote:
>
> I should’ve noticed that. Will resin and start another thread.
>
> This vote is now cancelled.
>
> -Anshum
>
>
>
>> On Aug 29, 2017, at 2:16 PM, Steve Rowe >
I should’ve noticed that. Will resin and start another thread.
This vote is now cancelled.
-Anshum
> On Aug 29, 2017, at 2:16 PM, Steve Rowe wrote:
>
> Hi Anshum,
>
> There is a 6.7.0 section in both Lucene's and Solr’s CHANGES.txt. I think
> you should respin after
Hi Anshum,
There is a 6.7.0 section in both Lucene's and Solr’s CHANGES.txt. I think you
should respin after merging the entries there under 7.0.0 section (on
branch_7_0, branch_7x and master; it should stay as-is on branch_6x).
--
Steve
www.lucidworks.com
> On Aug 29, 2017, at 4:02 PM,
I don't think this is worth a respin, specially as this is a UI only issue,
but if others have a different opinion we can reconsider.
On Tue, Aug 29, 2017 at 12:48 PM Shawn Heisey wrote:
> On 8/29/2017 11:36 AM, Anshum Gupta wrote:
> > Please vote for the first release
On 8/29/2017 11:36 AM, Anshum Gupta wrote:
> Please vote for the first release candidate for Apache Lucene/Solr 7.0.0.
Is SOLR-11296 (assuming the problem can be located and fixed quickly)
too small for a respin?
https://issues.apache.org/jira/browse/SOLR-11296
Thanks,
Shawn
Please vote for the first release candidate for Apache Lucene/Solr 7.0.0.Artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-7.0.0-RC1-rev5f7c00ed09fede00379a15eab3588e2134778994 You can run the smoke tester directly from this command: python3 -u