You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by jim ferenczi <ji...@gmail.com> on 2017/01/03 16:23:11 UTC
6.4 release
Hi,
I would like to volunteer to release 6.4. I can cut the release branch next
Monday if everybody agrees.
Jim
Re: 6.4 release
Posted by Andrzej Białecki <an...@lucidworks.com>.
> On 19 Jan 2017, at 15:01, jim ferenczi <ji...@gmail.com> wrote:
>
> I updated the release notes for Solr here:
> https://wiki.apache.org/solr/ReleaseNote64 <https://wiki.apache.org/solr/ReleaseNote64>
>
> The vote is going great so we may be able to start the release tomorrow night and make the announcement on Monday.
> We still need to finalize the release notes, could you please check that it's showing the right infos.
>
Notes look great. Minor issues:
* the first highlights section is titled “DocValues, streaming, …” but bullet points below don’t mention anything about DocValues.
* the section about metrics, first bullet point about metrics-jvm… I think it should just say in general that it uses Dropwizard Metrics API, and the bit about JVM internals should be moved to the second bullet point.
Thank you!
> 2017-01-17 18:51 GMT+01:00 Emmanuel Keller <keller.emmanuel@gmail.com <ma...@gmail.com>>:
> Thanks. It looks fine for me.
>
>
>> On 17 Jan 2017, at 18:37, jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com>> wrote:
>>
>> I added a line about DrillSideways in the new features since that's where it is in the CHANGES.txt but maybe it should be placed in the enhancement section ?
>>
>> 2017-01-17 18:29 GMT+01:00 Emmanuel Keller <keller.emmanuel@gmail.com <ma...@gmail.com>>:
>> Hi Jim,
>>
>> May I suggest to add this new feature from the Facet module ?
>>
>> A parallel DrillSideways implementation
>> https://issues.apache.org/jira/browse/LUCENE-7588 <https://issues.apache.org/jira/browse/LUCENE-7588>
>>
>> Emmanuel.
>>
>>
>>> On 17 Jan 2017, at 17:36, jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> I've created the release notes for Lucene and copied the template for Solr. I am not very familiar with the features/bugs/... to highlight for Solr in this release so any help would be greatly appreciated ;). For Lucene I wrote a first version that also needs review:
>>>
>>> https://wiki.apache.org/lucene-java/ReleaseNote64 <https://wiki.apache.org/lucene-java/ReleaseNote64>
>>> https://wiki.apache.org/solr/ReleaseNote64 <https://wiki.apache.org/solr/ReleaseNote64>
>>>
>>> Thanks,
>>> Jim
>>>
>>> 2017-01-17 14:31 GMT+01:00 jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com>>:
>>> Ok thanks David. I'll build the first RC now so your commit will be included.
>>>
>>> 2017-01-17 14:24 GMT+01:00 David Smiley <david.w.smiley@gmail.com <ma...@gmail.com>>:
>>> I just got in the hl.fragsize==0 special case for the SolrUnifiedHighlighter to branch master, 6x, 6.4
>>>
>>> There is a lingering question of the default for hl.maxAnalyzedChars https://issues.apache.org/jira/browse/SOLR-9708?focusedCommentId=15825503&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15825503 <https://issues.apache.org/jira/browse/SOLR-9708?focusedCommentId=15825503&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15825503> but it's not critical; maybe even wait for a second release candidate if that happens.
>>>
>>> On Tue, Jan 3, 2017 at 11:23 AM jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com>> wrote:
>>> Hi,
>>> I would like to volunteer to release 6.4. I can cut the release branch next Monday if everybody agrees.
>>>
>>>
>>> Jim
>>> --
>>> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
>>> LinkedIn: http://linkedin.com/in/davidwsmiley <http://linkedin.com/in/davidwsmiley> | Book: http://www.solrenterprisesearchserver.com <http://www.solrenterprisesearchserver.com/>
>>>
>>
>>
>
>
Re: 6.4 release
Posted by jim ferenczi <ji...@gmail.com>.
I updated the release notes for Solr here:
https://wiki.apache.org/solr/ReleaseNote64
The vote is going great so we may be able to start the release tomorrow
night and make the announcement on Monday.
We still need to finalize the release notes, could you please check that
it's showing the right infos.
Thanks
Jim
2017-01-17 18:51 GMT+01:00 Emmanuel Keller <ke...@gmail.com>:
> Thanks. It looks fine for me.
>
>
> On 17 Jan 2017, at 18:37, jim ferenczi <ji...@gmail.com> wrote:
>
> I added a line about DrillSideways in the new features since that's where
> it is in the CHANGES.txt but maybe it should be placed in the enhancement
> section ?
>
> 2017-01-17 18:29 GMT+01:00 Emmanuel Keller <ke...@gmail.com>:
>
>> Hi Jim,
>>
>> May I suggest to add this new feature from the Facet module ?
>>
>> A parallel DrillSideways implementation
>> https://issues.apache.org/jira/browse/LUCENE-7588
>>
>> Emmanuel.
>>
>>
>> On 17 Jan 2017, at 17:36, jim ferenczi <ji...@gmail.com> wrote:
>>
>> I've created the release notes for Lucene and copied the template for
>> Solr. I am not very familiar with the features/bugs/... to highlight for
>> Solr in this release so any help would be greatly appreciated ;). For
>> Lucene I wrote a first version that also needs review:
>>
>> https://wiki.apache.org/lucene-java/ReleaseNote64
>> https://wiki.apache.org/solr/ReleaseNote64
>>
>> Thanks,
>> Jim
>>
>> 2017-01-17 14:31 GMT+01:00 jim ferenczi <ji...@gmail.com>:
>>
>>> Ok thanks David. I'll build the first RC now so your commit will be
>>> included.
>>>
>>> 2017-01-17 14:24 GMT+01:00 David Smiley <da...@gmail.com>:
>>>
>>>> I just got in the hl.fragsize==0 special case for the
>>>> SolrUnifiedHighlighter to branch master, 6x, 6.4
>>>>
>>>> There is a lingering question of the default for hl.maxAnalyzedChars
>>>> https://issues.apache.org/jira/browse/SOLR-9708?focusedCommentId=15825
>>>> 503&page=com.atlassian.jira.plugin.system.issuetabpanels:com
>>>> ment-tabpanel#comment-15825503 but it's not critical; maybe even wait
>>>> for a second release candidate if that happens.
>>>>
>>>> On Tue, Jan 3, 2017 at 11:23 AM jim ferenczi <ji...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>> I would like to volunteer to release 6.4. I can cut the release
>>>>> branch next Monday if everybody agrees.
>>>>>
>>>>>
>>>>> Jim
>>>>>
>>>> --
>>>> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
>>>> LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
>>>> http://www.solrenterprisesearchserver.com
>>>>
>>>
>>>
>>
>>
>
>
Re: 6.4 release
Posted by Emmanuel Keller <ke...@gmail.com>.
Thanks. It looks fine for me.
> On 17 Jan 2017, at 18:37, jim ferenczi <ji...@gmail.com> wrote:
>
> I added a line about DrillSideways in the new features since that's where it is in the CHANGES.txt but maybe it should be placed in the enhancement section ?
>
> 2017-01-17 18:29 GMT+01:00 Emmanuel Keller <keller.emmanuel@gmail.com <ma...@gmail.com>>:
> Hi Jim,
>
> May I suggest to add this new feature from the Facet module ?
>
> A parallel DrillSideways implementation
> https://issues.apache.org/jira/browse/LUCENE-7588 <https://issues.apache.org/jira/browse/LUCENE-7588>
>
> Emmanuel.
>
>
>> On 17 Jan 2017, at 17:36, jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com>> wrote:
>>
>> I've created the release notes for Lucene and copied the template for Solr. I am not very familiar with the features/bugs/... to highlight for Solr in this release so any help would be greatly appreciated ;). For Lucene I wrote a first version that also needs review:
>>
>> https://wiki.apache.org/lucene-java/ReleaseNote64 <https://wiki.apache.org/lucene-java/ReleaseNote64>
>> https://wiki.apache.org/solr/ReleaseNote64 <https://wiki.apache.org/solr/ReleaseNote64>
>>
>> Thanks,
>> Jim
>>
>> 2017-01-17 14:31 GMT+01:00 jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com>>:
>> Ok thanks David. I'll build the first RC now so your commit will be included.
>>
>> 2017-01-17 14:24 GMT+01:00 David Smiley <david.w.smiley@gmail.com <ma...@gmail.com>>:
>> I just got in the hl.fragsize==0 special case for the SolrUnifiedHighlighter to branch master, 6x, 6.4
>>
>> There is a lingering question of the default for hl.maxAnalyzedChars https://issues.apache.org/jira/browse/SOLR-9708?focusedCommentId=15825503&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15825503 <https://issues.apache.org/jira/browse/SOLR-9708?focusedCommentId=15825503&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15825503> but it's not critical; maybe even wait for a second release candidate if that happens.
>>
>> On Tue, Jan 3, 2017 at 11:23 AM jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com>> wrote:
>> Hi,
>> I would like to volunteer to release 6.4. I can cut the release branch next Monday if everybody agrees.
>>
>>
>> Jim
>> --
>> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
>> LinkedIn: http://linkedin.com/in/davidwsmiley <http://linkedin.com/in/davidwsmiley> | Book: http://www.solrenterprisesearchserver.com <http://www.solrenterprisesearchserver.com/>
>>
>
>
Re: 6.4 release
Posted by jim ferenczi <ji...@gmail.com>.
I added a line about DrillSideways in the new features since that's where
it is in the CHANGES.txt but maybe it should be placed in the enhancement
section ?
2017-01-17 18:29 GMT+01:00 Emmanuel Keller <ke...@gmail.com>:
> Hi Jim,
>
> May I suggest to add this new feature from the Facet module ?
>
> A parallel DrillSideways implementation
> https://issues.apache.org/jira/browse/LUCENE-7588
>
> Emmanuel.
>
>
> On 17 Jan 2017, at 17:36, jim ferenczi <ji...@gmail.com> wrote:
>
> I've created the release notes for Lucene and copied the template for
> Solr. I am not very familiar with the features/bugs/... to highlight for
> Solr in this release so any help would be greatly appreciated ;). For
> Lucene I wrote a first version that also needs review:
>
> https://wiki.apache.org/lucene-java/ReleaseNote64
> https://wiki.apache.org/solr/ReleaseNote64
>
> Thanks,
> Jim
>
> 2017-01-17 14:31 GMT+01:00 jim ferenczi <ji...@gmail.com>:
>
>> Ok thanks David. I'll build the first RC now so your commit will be
>> included.
>>
>> 2017-01-17 14:24 GMT+01:00 David Smiley <da...@gmail.com>:
>>
>>> I just got in the hl.fragsize==0 special case for the
>>> SolrUnifiedHighlighter to branch master, 6x, 6.4
>>>
>>> There is a lingering question of the default for hl.maxAnalyzedChars
>>> https://issues.apache.org/jira/browse/SOLR-9708?focusedCommentId=15825
>>> 503&page=com.atlassian.jira.plugin.system.issuetabpanels:com
>>> ment-tabpanel#comment-15825503 but it's not critical; maybe even wait
>>> for a second release candidate if that happens.
>>>
>>> On Tue, Jan 3, 2017 at 11:23 AM jim ferenczi <ji...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>> I would like to volunteer to release 6.4. I can cut the release branch
>>>> next Monday if everybody agrees.
>>>>
>>>>
>>>> Jim
>>>>
>>> --
>>> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
>>> LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
>>> http://www.solrenterprisesearchserver.com
>>>
>>
>>
>
>
Re: 6.4 release
Posted by Emmanuel Keller <ke...@gmail.com>.
Hi Jim,
May I suggest to add this new feature from the Facet module ?
A parallel DrillSideways implementation
https://issues.apache.org/jira/browse/LUCENE-7588 <https://issues.apache.org/jira/browse/LUCENE-7588>
Emmanuel.
> On 17 Jan 2017, at 17:36, jim ferenczi <ji...@gmail.com> wrote:
>
> I've created the release notes for Lucene and copied the template for Solr. I am not very familiar with the features/bugs/... to highlight for Solr in this release so any help would be greatly appreciated ;). For Lucene I wrote a first version that also needs review:
>
> https://wiki.apache.org/lucene-java/ReleaseNote64 <https://wiki.apache.org/lucene-java/ReleaseNote64>
> https://wiki.apache.org/solr/ReleaseNote64 <https://wiki.apache.org/solr/ReleaseNote64>
>
> Thanks,
> Jim
>
> 2017-01-17 14:31 GMT+01:00 jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com>>:
> Ok thanks David. I'll build the first RC now so your commit will be included.
>
> 2017-01-17 14:24 GMT+01:00 David Smiley <david.w.smiley@gmail.com <ma...@gmail.com>>:
> I just got in the hl.fragsize==0 special case for the SolrUnifiedHighlighter to branch master, 6x, 6.4
>
> There is a lingering question of the default for hl.maxAnalyzedChars https://issues.apache.org/jira/browse/SOLR-9708?focusedCommentId=15825503&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15825503 <https://issues.apache.org/jira/browse/SOLR-9708?focusedCommentId=15825503&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15825503> but it's not critical; maybe even wait for a second release candidate if that happens.
>
> On Tue, Jan 3, 2017 at 11:23 AM jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com>> wrote:
> Hi,
> I would like to volunteer to release 6.4. I can cut the release branch next Monday if everybody agrees.
>
>
> Jim
> --
> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
> LinkedIn: http://linkedin.com/in/davidwsmiley <http://linkedin.com/in/davidwsmiley> | Book: http://www.solrenterprisesearchserver.com <http://www.solrenterprisesearchserver.com/>
>
Re: 6.4 release
Posted by jim ferenczi <ji...@gmail.com>.
I've created the release notes for Lucene and copied the template for Solr.
I am not very familiar with the features/bugs/... to highlight for Solr in
this release so any help would be greatly appreciated ;). For Lucene I
wrote a first version that also needs review:
https://wiki.apache.org/lucene-java/ReleaseNote64
https://wiki.apache.org/solr/ReleaseNote64
Thanks,
Jim
2017-01-17 14:31 GMT+01:00 jim ferenczi <ji...@gmail.com>:
> Ok thanks David. I'll build the first RC now so your commit will be
> included.
>
> 2017-01-17 14:24 GMT+01:00 David Smiley <da...@gmail.com>:
>
>> I just got in the hl.fragsize==0 special case for the
>> SolrUnifiedHighlighter to branch master, 6x, 6.4
>>
>> There is a lingering question of the default for hl.maxAnalyzedChars
>> https://issues.apache.org/jira/browse/SOLR-9708?focusedCommentId=15825
>> 503&page=com.atlassian.jira.plugin.system.issuetabpanels:
>> comment-tabpanel#comment-15825503 but it's not critical; maybe even
>> wait for a second release candidate if that happens.
>>
>> On Tue, Jan 3, 2017 at 11:23 AM jim ferenczi <ji...@gmail.com>
>> wrote:
>>
>>> Hi,
>>> I would like to volunteer to release 6.4. I can cut the release branch
>>> next Monday if everybody agrees.
>>>
>>>
>>> Jim
>>>
>> --
>> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
>> LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
>> http://www.solrenterprisesearchserver.com
>>
>
>
Re: 6.4 release
Posted by jim ferenczi <ji...@gmail.com>.
Ok thanks David. I'll build the first RC now so your commit will be
included.
2017-01-17 14:24 GMT+01:00 David Smiley <da...@gmail.com>:
> I just got in the hl.fragsize==0 special case for the
> SolrUnifiedHighlighter to branch master, 6x, 6.4
>
> There is a lingering question of the default for hl.maxAnalyzedChars
> https://issues.apache.org/jira/browse/SOLR-9708?focusedCommentId=
> 15825503&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel#comment-15825503 but it's not critical; maybe even wait for a
> second release candidate if that happens.
>
> On Tue, Jan 3, 2017 at 11:23 AM jim ferenczi <ji...@gmail.com>
> wrote:
>
>> Hi,
>> I would like to volunteer to release 6.4. I can cut the release branch
>> next Monday if everybody agrees.
>>
>>
>> Jim
>>
> --
> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
> LinkedIn: http://linkedin.com/in/davidwsmiley | Book: http://www.
> solrenterprisesearchserver.com
>
Re: 6.4 release
Posted by David Smiley <da...@gmail.com>.
I just got in the hl.fragsize==0 special case for the
SolrUnifiedHighlighter to branch master, 6x, 6.4
There is a lingering question of the default for hl.maxAnalyzedChars
https://issues.apache.org/jira/browse/SOLR-9708?focusedCommentId=15825503&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15825503
but it's not critical; maybe even wait for a second release candidate if
that happens.
On Tue, Jan 3, 2017 at 11:23 AM jim ferenczi <ji...@gmail.com> wrote:
> Hi,
> I would like to volunteer to release 6.4. I can cut the release branch
> next Monday if everybody agrees.
>
>
> Jim
>
--
Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
http://www.solrenterprisesearchserver.com
Re: 6.4 release
Posted by Adrien Grand <jp...@gmail.com>.
+1 to cut the 6.4 branch and build a RC next monday
Le mer. 4 janv. 2017 à 07:39, Andrzej Białecki <
andrzej.bialecki@lucidworks.com> a écrit :
> On 4 Jan 2017, at 05:00, Walter Underwood <wu...@wunderwood.org> wrote:
>
> If the metrics changes get in, I will be very, very happy. We’ve been
> running with local hacks for four years.
>
>
>
> Most of the key instrumentation is already in place. Shalin and I are
> working now on cloud-related metrics (transaction log metrics, aggregated
> metrics from replicas and from shard leaders). There’s one improvement that
> would be good to put into 6.4: SOLR-9911 Add a way to filter metrics by
> prefix in the MetricsHandler API. This would help a lot in optimizing the
> retrieval of selected metrics, from among the hundreds that we track now.
>
> Andrzej
>
> wunder
> Walter Underwood
> wunder@wunderwood.org
> http://observer.wunderwood.org/ (my blog)
>
>
> On Jan 3, 2017, at 9:25 AM, Michael McCandless <lu...@mikemccandless.com>
> wrote:
>
> +1, lots of good stuff for 6.4 already! Thanks for volunteering Jim :)
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Tue, Jan 3, 2017 at 11:23 AM, jim ferenczi <ji...@gmail.com>
> wrote:
>
> Hi,
> I would like to volunteer to release 6.4. I can cut the release branch next
> Monday if everybody agrees.
>
> Jim
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
>
Re: 6.4 release
Posted by Andrzej Białecki <an...@lucidworks.com>.
> On 4 Jan 2017, at 05:00, Walter Underwood <wu...@wunderwood.org> wrote:
>
> If the metrics changes get in, I will be very, very happy. We’ve been running with local hacks for four years.
>
Most of the key instrumentation is already in place. Shalin and I are working now on cloud-related metrics (transaction log metrics, aggregated metrics from replicas and from shard leaders). There’s one improvement that would be good to put into 6.4: SOLR-9911 Add a way to filter metrics by prefix in the MetricsHandler API. This would help a lot in optimizing the retrieval of selected metrics, from among the hundreds that we track now.
Andrzej
> wunder
> Walter Underwood
> wunder@wunderwood.org <ma...@wunderwood.org>
> http://observer.wunderwood.org/ (my blog)
>
>
>> On Jan 3, 2017, at 9:25 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
>>
>> +1, lots of good stuff for 6.4 already! Thanks for volunteering Jim :)
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>>
>>
>> On Tue, Jan 3, 2017 at 11:23 AM, jim ferenczi <ji...@gmail.com> wrote:
>>> Hi,
>>> I would like to volunteer to release 6.4. I can cut the release branch next
>>> Monday if everybody agrees.
>>>
>>> Jim
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
Re: 6.4 release
Posted by Walter Underwood <wu...@wunderwood.org>.
If the metrics changes get in, I will be very, very happy. We’ve been running with local hacks for four years.
wunder
Walter Underwood
wunder@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jan 3, 2017, at 9:25 AM, Michael McCandless <lu...@mikemccandless.com> wrote:
>
> +1, lots of good stuff for 6.4 already! Thanks for volunteering Jim :)
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Tue, Jan 3, 2017 at 11:23 AM, jim ferenczi <ji...@gmail.com> wrote:
>> Hi,
>> I would like to volunteer to release 6.4. I can cut the release branch next
>> Monday if everybody agrees.
>>
>> Jim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
Re: 6.4 release
Posted by Anshum Gupta <an...@anshumgupta.net>.
Thanks for volunteering Jim!
I have some stuff that I'd like to get in, but nothing that's a show
stopper.
-Anshum
On Tue, Jan 3, 2017 at 10:23 AM Joel Bernstein <jo...@gmail.com> wrote:
> +1. I still have a little more work to do for 6.4 but I should have it all
> committed by end of day tomorrow.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Tue, Jan 3, 2017 at 12:25 PM, Michael McCandless <
> lucene@mikemccandless.com> wrote:
>
> +1, lots of good stuff for 6.4 already! Thanks for volunteering Jim :)
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Tue, Jan 3, 2017 at 11:23 AM, jim ferenczi <ji...@gmail.com>
> wrote:
> > Hi,
> > I would like to volunteer to release 6.4. I can cut the release branch
> next
> > Monday if everybody agrees.
> >
> > Jim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
>
Re: 6.4 release
Posted by Joel Bernstein <jo...@gmail.com>.
+1. I still have a little more work to do for 6.4 but I should have it all
committed by end of day tomorrow.
Joel Bernstein
http://joelsolr.blogspot.com/
On Tue, Jan 3, 2017 at 12:25 PM, Michael McCandless <
lucene@mikemccandless.com> wrote:
> +1, lots of good stuff for 6.4 already! Thanks for volunteering Jim :)
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Tue, Jan 3, 2017 at 11:23 AM, jim ferenczi <ji...@gmail.com>
> wrote:
> > Hi,
> > I would like to volunteer to release 6.4. I can cut the release branch
> next
> > Monday if everybody agrees.
> >
> > Jim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: 6.4 release
Posted by Michael McCandless <lu...@mikemccandless.com>.
+1, lots of good stuff for 6.4 already! Thanks for volunteering Jim :)
Mike McCandless
http://blog.mikemccandless.com
On Tue, Jan 3, 2017 at 11:23 AM, jim ferenczi <ji...@gmail.com> wrote:
> Hi,
> I would like to volunteer to release 6.4. I can cut the release branch next
> Monday if everybody agrees.
>
> Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: 6.4 release
Posted by Alan Woodward <al...@flax.co.uk>.
Hi Jim,
I’d like to get LUCENE-7609, LUCENE-7610 and LUCENE-7611 in - I’ll commit them over the weekend unless anybody squawks.
Alan Woodward
www.flax.co.uk
> On 6 Jan 2017, at 18:22, jim ferenczi <ji...@gmail.com> wrote:
>
> Thanks all for your answers.
> Are we still good to build the first RC on Monday ? Christine maybe do you need more time ?
>
>
> 2017-01-05 5:47 GMT+01:00 Shalin Shekhar Mangar <shalinmangar@gmail.com <ma...@gmail.com>>:
> Aggregated metrics will not be in 6.4 -- that work is still in progress.
>
> On Thu, Jan 5, 2017 at 6:57 AM, S G <sg.online.email@gmail.com <ma...@gmail.com>> wrote:
> > +1 for adding the metric related changes.
> > Aggregated metrics from from replicas sounds like a very nice thing to have.
> >
> > On Wed, Jan 4, 2017 at 12:11 PM, Varun Thacker <varun@vthacker.in <ma...@vthacker.in>> wrote:
> >>
> >> +1 to cut a release branch on monday. Lots of goodies in this release!
> >>
> >> On Tue, Jan 3, 2017 at 8:23 AM, jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com>>
> >> wrote:
> >>>
> >>> Hi,
> >>> I would like to volunteer to release 6.4. I can cut the release branch
> >>> next Monday if everybody agrees.
> >>>
> >>> Jim
> >>
> >>
> >
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>
> ---------------------------------------------------------------------
> 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>
>
>
Re: 6.4 release
Posted by Joel Bernstein <jo...@gmail.com>.
I'm all done with 6.4 changes.
Joel Bernstein
http://joelsolr.blogspot.com/
On Fri, Jan 6, 2017 at 1:22 PM, jim ferenczi <ji...@gmail.com> wrote:
> Thanks all for your answers.
> Are we still good to build the first RC on Monday ? Christine maybe do you
> need more time ?
>
>
> 2017-01-05 5:47 GMT+01:00 Shalin Shekhar Mangar <sh...@gmail.com>:
>
>> Aggregated metrics will not be in 6.4 -- that work is still in progress.
>>
>> On Thu, Jan 5, 2017 at 6:57 AM, S G <sg...@gmail.com> wrote:
>> > +1 for adding the metric related changes.
>> > Aggregated metrics from from replicas sounds like a very nice thing to
>> have.
>> >
>> > On Wed, Jan 4, 2017 at 12:11 PM, Varun Thacker <va...@vthacker.in>
>> wrote:
>> >>
>> >> +1 to cut a release branch on monday. Lots of goodies in this release!
>> >>
>> >> On Tue, Jan 3, 2017 at 8:23 AM, jim ferenczi <ji...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi,
>> >>> I would like to volunteer to release 6.4. I can cut the release branch
>> >>> next Monday if everybody agrees.
>> >>>
>> >>> Jim
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Regards,
>> Shalin Shekhar Mangar.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: 6.4 release
Posted by jim ferenczi <ji...@gmail.com>.
Thanks all for your answers.
Are we still good to build the first RC on Monday ? Christine maybe do you
need more time ?
2017-01-05 5:47 GMT+01:00 Shalin Shekhar Mangar <sh...@gmail.com>:
> Aggregated metrics will not be in 6.4 -- that work is still in progress.
>
> On Thu, Jan 5, 2017 at 6:57 AM, S G <sg...@gmail.com> wrote:
> > +1 for adding the metric related changes.
> > Aggregated metrics from from replicas sounds like a very nice thing to
> have.
> >
> > On Wed, Jan 4, 2017 at 12:11 PM, Varun Thacker <va...@vthacker.in>
> wrote:
> >>
> >> +1 to cut a release branch on monday. Lots of goodies in this release!
> >>
> >> On Tue, Jan 3, 2017 at 8:23 AM, jim ferenczi <ji...@gmail.com>
> >> wrote:
> >>>
> >>> Hi,
> >>> I would like to volunteer to release 6.4. I can cut the release branch
> >>> next Monday if everybody agrees.
> >>>
> >>> Jim
> >>
> >>
> >
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: 6.4 release
Posted by Shalin Shekhar Mangar <sh...@gmail.com>.
Aggregated metrics will not be in 6.4 -- that work is still in progress.
On Thu, Jan 5, 2017 at 6:57 AM, S G <sg...@gmail.com> wrote:
> +1 for adding the metric related changes.
> Aggregated metrics from from replicas sounds like a very nice thing to have.
>
> On Wed, Jan 4, 2017 at 12:11 PM, Varun Thacker <va...@vthacker.in> wrote:
>>
>> +1 to cut a release branch on monday. Lots of goodies in this release!
>>
>> On Tue, Jan 3, 2017 at 8:23 AM, jim ferenczi <ji...@gmail.com>
>> wrote:
>>>
>>> Hi,
>>> I would like to volunteer to release 6.4. I can cut the release branch
>>> next Monday if everybody agrees.
>>>
>>> Jim
>>
>>
>
--
Regards,
Shalin Shekhar Mangar.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: 6.4 release
Posted by S G <sg...@gmail.com>.
+1 for adding the metric related changes.
Aggregated metrics from from replicas sounds like a very nice thing to have.
On Wed, Jan 4, 2017 at 12:11 PM, Varun Thacker <va...@vthacker.in> wrote:
> +1 to cut a release branch on monday. Lots of goodies in this release!
>
> On Tue, Jan 3, 2017 at 8:23 AM, jim ferenczi <ji...@gmail.com>
> wrote:
>
>> Hi,
>> I would like to volunteer to release 6.4. I can cut the release branch
>> next Monday if everybody agrees.
>>
>> Jim
>>
>
>
Re: 6.4 release
Posted by Varun Thacker <va...@vthacker.in>.
+1 to cut a release branch on monday. Lots of goodies in this release!
On Tue, Jan 3, 2017 at 8:23 AM, jim ferenczi <ji...@gmail.com> wrote:
> Hi,
> I would like to volunteer to release 6.4. I can cut the release branch
> next Monday if everybody agrees.
>
> Jim
>
Re: 6.4 release
Posted by David Smiley <da...@gmail.com>.
I re-openned https://issues.apache.org/jira/browse/LUCENE-7559 -- I should
be able to fix tonight easily enough.
On Tue, Jan 3, 2017 at 11:23 AM jim ferenczi <ji...@gmail.com> wrote:
> Hi,
> I would like to volunteer to release 6.4. I can cut the release branch
> next Monday if everybody agrees.
>
>
> Jim
>
--
Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
http://www.solrenterprisesearchserver.com
Re: 6.4 release
Posted by Mark Miller <ma...@gmail.com>.
Create a jira and someone will update it for the next release.
On Fri, Jan 13, 2017 at 7:47 PM S G <sg...@gmail.com> wrote:
> Probably too late for this release, but can we consider using Zookeeper
> 3.4.9 for the next
> release as it brings in a lot of stability improvements (
> http://zookeeper.apache.org/releases.html) and
> Solr guide is still recommending zookeeper 3.4.6 (
> https://cwiki.apache.org/confluence/display/solr/Setting+Up+an+External+ZooKeeper+Ensemble
> )
>
> On Fri, Jan 13, 2017 at 11:46 AM, jim ferenczi <ji...@gmail.com>
> wrote:
>
> Great news Uwe! I'll cut the branch this week end if nobody disagree.
>
> Le 13 janv. 2017 20:24, "Uwe Schindler" <uw...@thetaphi.de> a écrit :
>
> Hi Jim,
>
>
>
> I updated Groovy. I’d like to run Solr tests this evening through Jenkins
> with Java 9 EA build 151 to get a list of all tests that have to be
> disabled for Java 9, but otherwise we are ready.
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> Achterdiek 19, D-28357 Bremen
>
> http://www.thetaphi.de
>
> eMail: uwe@thetaphi.de
>
>
>
> *From:* jim ferenczi [mailto:jim.ferenczi@gmail.com]
> *Sent:* Monday, January 9, 2017 12:37 PM
> *To:* dev@lucene.apache.org
> *Subject:* Re: 6.4 release
>
>
>
> Thanks for sharing Uwe. It would be wonderful to make latest java9 works
> with the released version. I can delay the branching until
> https://issues.apache.org/jira/browse/LUCENE-7596 is closed ?
>
> In the mean time I am trying to create the release notes in the wiki but I
> don't have the permissions to create the pages. Where can I get such
> permissions ?
>
>
>
> 2017-01-09 11:13 GMT+01:00 Uwe Schindler <uw...@thetaphi.de>:
>
> Hi,
>
>
>
> I am fine with the start of release process, but I would like to add one
> thing:
>
>
>
> I know that Elasticsearch wants to be compatible with recent Java 9 for
> the continuous delievery process. The new Lucene release is compatible with
> that (mmap unmapping works), but you cannot build the release with Java 9
> 148+. Currently the release vote of Groovy 2.4.8 is ongoing and should
> finish the next few days. So I’d suggest to delay a bit, so I can update
> common-build.xml and raise the Groovy version:
> https://issues.apache.org/jira/browse/LUCENE-7596
>
>
>
> This does not make Solr Tests work with Java 9, but that’s a different
> discussion (mocking frameworks broke with recent Java 9):
> https://issues.apache.org/jira/browse/SOLR-9893
>
> I will fix this by disabling those tests with Java 9, but that a bit of
> work to set those assumeFalse(Constants.JAVA9….). I don’t see this as a
> blocker!
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> Achterdiek 19, D-28357 Bremen
>
> http://www.thetaphi.de
>
> eMail: uwe@thetaphi.de
>
>
>
> *From:* jim ferenczi [mailto:jim.ferenczi@gmail.com]
> *Sent:* Tuesday, January 3, 2017 5:23 PM
> *To:* dev@lucene.apache.org
> *Subject:* 6.4 release
>
>
>
> Hi,
> I would like to volunteer to release 6.4. I can cut the release branch
> next Monday if everybody agrees.
>
>
>
> Jim
>
>
>
>
> --
- Mark
about.me/markrmiller
Re: 6.4 release
Posted by S G <sg...@gmail.com>.
Probably too late for this release, but can we consider using Zookeeper
3.4.9 for the next
release as it brings in a lot of stability improvements (
http://zookeeper.apache.org/releases.html) and
Solr guide is still recommending zookeeper 3.4.6 (
https://cwiki.apache.org/confluence/display/solr/Setting+Up+an+External+ZooKeeper+Ensemble
)
On Fri, Jan 13, 2017 at 11:46 AM, jim ferenczi <ji...@gmail.com>
wrote:
> Great news Uwe! I'll cut the branch this week end if nobody disagree.
>
> Le 13 janv. 2017 20:24, "Uwe Schindler" <uw...@thetaphi.de> a écrit :
>
>> Hi Jim,
>>
>>
>>
>> I updated Groovy. I’d like to run Solr tests this evening through Jenkins
>> with Java 9 EA build 151 to get a list of all tests that have to be
>> disabled for Java 9, but otherwise we are ready.
>>
>>
>>
>> Uwe
>>
>>
>>
>> -----
>>
>> Uwe Schindler
>>
>> Achterdiek 19, D-28357 Bremen
>>
>> http://www.thetaphi.de
>>
>> eMail: uwe@thetaphi.de
>>
>>
>>
>> *From:* jim ferenczi [mailto:jim.ferenczi@gmail.com]
>> *Sent:* Monday, January 9, 2017 12:37 PM
>> *To:* dev@lucene.apache.org
>> *Subject:* Re: 6.4 release
>>
>>
>>
>> Thanks for sharing Uwe. It would be wonderful to make latest java9 works
>> with the released version. I can delay the branching until
>> https://issues.apache.org/jira/browse/LUCENE-7596 is closed ?
>>
>> In the mean time I am trying to create the release notes in the wiki but
>> I don't have the permissions to create the pages. Where can I get such
>> permissions ?
>>
>>
>>
>> 2017-01-09 11:13 GMT+01:00 Uwe Schindler <uw...@thetaphi.de>:
>>
>> Hi,
>>
>>
>>
>> I am fine with the start of release process, but I would like to add one
>> thing:
>>
>>
>>
>> I know that Elasticsearch wants to be compatible with recent Java 9 for
>> the continuous delievery process. The new Lucene release is compatible with
>> that (mmap unmapping works), but you cannot build the release with Java 9
>> 148+. Currently the release vote of Groovy 2.4.8 is ongoing and should
>> finish the next few days. So I’d suggest to delay a bit, so I can update
>> common-build.xml and raise the Groovy version:
>> https://issues.apache.org/jira/browse/LUCENE-7596
>>
>>
>>
>> This does not make Solr Tests work with Java 9, but that’s a different
>> discussion (mocking frameworks broke with recent Java 9):
>> https://issues.apache.org/jira/browse/SOLR-9893
>>
>> I will fix this by disabling those tests with Java 9, but that a bit of
>> work to set those assumeFalse(Constants.JAVA9….). I don’t see this as a
>> blocker!
>>
>>
>>
>> Uwe
>>
>>
>>
>> -----
>>
>> Uwe Schindler
>>
>> Achterdiek 19, D-28357 Bremen
>>
>> http://www.thetaphi.de
>>
>> eMail: uwe@thetaphi.de
>>
>>
>>
>> *From:* jim ferenczi [mailto:jim.ferenczi@gmail.com]
>> *Sent:* Tuesday, January 3, 2017 5:23 PM
>> *To:* dev@lucene.apache.org
>> *Subject:* 6.4 release
>>
>>
>>
>> Hi,
>> I would like to volunteer to release 6.4. I can cut the release branch
>> next Monday if everybody agrees.
>>
>>
>>
>> Jim
>>
>>
>>
>
RE: 6.4 release
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi David,
I fixed it already, see: https://git1-us-west.apache.org/repos/asf?p=lucene-solr.git;a=commit;h=60d4a554
It was the LuceneRegexFragmenter class that caused this. Maybe it existed before, too, but the changes recently added for UnifiedHighlighter caused the trouble for eclipse. I have no idea why, but since git pull, Eclipse complained loud for several days.
Now it is fine again,
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
<http://www.thetaphi.de/> http://www.thetaphi.de
eMail: uwe@thetaphi.de
From: David Smiley [mailto:david.w.smiley@gmail.com]
Sent: Monday, January 16, 2017 4:19 AM
To: dev@lucene.apache.org
Subject: Re: 6.4 release
Hello Uwe,
On Sat, Jan 14, 2017 at 1:56 PM Uwe Schindler < <ma...@thetaphi.de> uwe@thetaphi.de> wrote:
Hi,
I fixed the compile warning. The more serious issue was a problem with Solr and Eclipse: It did not compile anymore, because the Solr UHighlighter implementation was using a Java-1.0-like inner class which was not nested but just top-level in same source file.
Can you please clarify what this problem is? I thought I knew but your example doesn't match my understanding. I don't use Eclipse so it's not apparent to me. UnifiedSolrHighlighter has a static inner class SolrExtendedUnifiedHighlighter. It is an inner class; not some other class in the same source file. UnifiedHighlither (in Lucene) only has inner classes too. Maybe you meant the class FragmentQueue in Lucene Highlighter.java? I dunno.
IMHO, we should add a style check in “ant validate” to prevent this type of class declaration. Top-Level classes should always be in separate files or properly nested.
+1
~ David
--
Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
LinkedIn: http://linkedin.com/in/davidwsmiley | Book: http://www.solrenterprisesearchserver.com
Re: 6.4 release
Posted by David Smiley <da...@gmail.com>.
Hello Uwe,
On Sat, Jan 14, 2017 at 1:56 PM Uwe Schindler <uw...@thetaphi.de> wrote:
> Hi,
>
>
>
> I fixed the compile warning. The more serious issue was a problem with
> Solr and Eclipse: It did not compile anymore, because the Solr UHighlighter
> implementation was using a Java-1.0-like inner class which was not nested
> but just top-level in same source file.
>
Can you please clarify what this problem is? I thought I knew but your
example doesn't match my understanding. I don't use Eclipse so it's not
apparent to me. UnifiedSolrHighlighter has a static inner class
SolrExtendedUnifiedHighlighter. It is an inner class; not some other class
in the same source file. UnifiedHighlither (in Lucene) only has inner
classes too. Maybe you meant the class FragmentQueue in Lucene
Highlighter.java? I dunno.
> IMHO, we should add a style check in “ant validate” to prevent this type
> of class declaration. Top-Level classes should always be in separate files
> or properly nested.
>
+1
~ David
--
Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
http://www.solrenterprisesearchserver.com
RE: 6.4 release
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
I fixed the compile warning. The more serious issue was a problem with Solr and Eclipse: It did not compile anymore, because the Solr UHighlighter implementation was using a Java-1.0-like inner class which was not nested but just top-level in same source file.
IMHO, we should add a style check in “ant validate” to prevent this type of class declaration. Top-Level classes should always be in separate files or properly nested.
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: uwe@thetaphi.de
From: Uwe Schindler [mailto:uwe@thetaphi.de]
Sent: Saturday, January 14, 2017 7:31 PM
To: dev@lucene.apache.org
Subject: RE: 6.4 release
One final thing:
Would it be possible to nuke the stupid unchecked warning caused by CollectorManager before release? We always tried to keep at least Lucene Core to compile without warnings, and now it’s really noisy and especially it is the first you see during build! Not a good sign :(
I can try to fix this, but this would require to commit to 6.4 branch.
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: <ma...@thetaphi.de> uwe@thetaphi.de
From: Uwe Schindler [ <ma...@thetaphi.de> mailto:uwe@thetaphi.de]
Sent: Saturday, January 14, 2017 7:25 PM
To: <ma...@lucene.apache.org> dev@lucene.apache.org
Subject: RE: 6.4 release
Hi Jim,
Jenkins Jobs created and triggered for build!
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: <ma...@thetaphi.de> uwe@thetaphi.de
From: jim ferenczi [ <ma...@gmail.com> mailto:jim.ferenczi@gmail.com]
Sent: Saturday, January 14, 2017 4:03 PM
To: <ma...@lucene.apache.org> dev@lucene.apache.org
Subject: Re: 6.4 release
Thanks Uwe !
2017-01-14 16:01 GMT+01:00 Uwe Schindler <uwe@thetaphi.de <ma...@thetaphi.de> >:
Hi Jim,
Thanks! I will update Jenkins this evening (Policeman and ASF).
The first successful Java 9 build 152 was executed already on branch-6x, so we are in good shape also on Java 9 front. 😎
Uwe
Am 14. Januar 2017 15:57:13 MEZ schrieb jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com> >:
Hi,
The release branch for 6.4 is pushed so the feature freeze phase has officially started.
I don't have an admin account on Jenkins so any help would be appreciated. We need to copy the job for the new branch.
No new features may be committed to the branch.
Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
Only Jira issues with Fix version "6.4" and priority "Blocker" will delay a release candidate build.
Thanks,
Jim
--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de
RE: 6.4 release
Posted by Uwe Schindler <uw...@thetaphi.de>.
One final thing:
Would it be possible to nuke the stupid unchecked warning caused by CollectorManager before release? We always tried to keep at least Lucene Core to compile without warnings, and now it’s really noisy and especially it is the first you see during build! Not a good sign :(
I can try to fix this, but this would require to commit to 6.4 branch.
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: uwe@thetaphi.de
From: Uwe Schindler [mailto:uwe@thetaphi.de]
Sent: Saturday, January 14, 2017 7:25 PM
To: dev@lucene.apache.org
Subject: RE: 6.4 release
Hi Jim,
Jenkins Jobs created and triggered for build!
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: <ma...@thetaphi.de> uwe@thetaphi.de
From: jim ferenczi [ <ma...@gmail.com> mailto:jim.ferenczi@gmail.com]
Sent: Saturday, January 14, 2017 4:03 PM
To: <ma...@lucene.apache.org> dev@lucene.apache.org
Subject: Re: 6.4 release
Thanks Uwe !
2017-01-14 16:01 GMT+01:00 Uwe Schindler <uwe@thetaphi.de <ma...@thetaphi.de> >:
Hi Jim,
Thanks! I will update Jenkins this evening (Policeman and ASF).
The first successful Java 9 build 152 was executed already on branch-6x, so we are in good shape also on Java 9 front. 😎
Uwe
Am 14. Januar 2017 15:57:13 MEZ schrieb jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com> >:
Hi,
The release branch for 6.4 is pushed so the feature freeze phase has officially started.
I don't have an admin account on Jenkins so any help would be appreciated. We need to copy the job for the new branch.
No new features may be committed to the branch.
Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
Only Jira issues with Fix version "6.4" and priority "Blocker" will delay a release candidate build.
Thanks,
Jim
--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de
RE: 6.4 release
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi Jim,
Jenkins Jobs created and triggered for build!
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: uwe@thetaphi.de
From: jim ferenczi [mailto:jim.ferenczi@gmail.com]
Sent: Saturday, January 14, 2017 4:03 PM
To: dev@lucene.apache.org
Subject: Re: 6.4 release
Thanks Uwe !
2017-01-14 16:01 GMT+01:00 Uwe Schindler <uwe@thetaphi.de <ma...@thetaphi.de> >:
Hi Jim,
Thanks! I will update Jenkins this evening (Policeman and ASF).
The first successful Java 9 build 152 was executed already on branch-6x, so we are in good shape also on Java 9 front. 😎
Uwe
Am 14. Januar 2017 15:57:13 MEZ schrieb jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com> >:
Hi,
The release branch for 6.4 is pushed so the feature freeze phase has officially started.
I don't have an admin account on Jenkins so any help would be appreciated. We need to copy the job for the new branch.
No new features may be committed to the branch.
Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
Only Jira issues with Fix version "6.4" and priority "Blocker" will delay a release candidate build.
Thanks,
Jim
--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de
Re: 6.4 release
Posted by S G <sg...@gmail.com>.
Created https://issues.apache.org/jira/browse/SOLR-9967 as per Mark's
request.
On Sat, Jan 14, 2017 at 7:02 AM, jim ferenczi <ji...@gmail.com>
wrote:
> Thanks Uwe !
>
> 2017-01-14 16:01 GMT+01:00 Uwe Schindler <uw...@thetaphi.de>:
>
>> Hi Jim,
>>
>> Thanks! I will update Jenkins this evening (Policeman and ASF).
>>
>> The first successful Java 9 build 152 was executed already on branch-6x,
>> so we are in good shape also on Java 9 front. 😎
>>
>> Uwe
>>
>>
>> Am 14. Januar 2017 15:57:13 MEZ schrieb jim ferenczi <
>> jim.ferenczi@gmail.com>:
>>>
>>> Hi,
>>>
>>> The release branch for 6.4 is pushed so the feature freeze phase has
>>> officially started.
>>> I don't have an admin account on Jenkins so any help would be
>>> appreciated. We need to copy the job for the new branch.
>>>
>>> No new features may be committed to the branch.
>>> Documentation patches, build patches and serious bug fixes may be
>>> committed to the branch. However, you should submit all patches you want to
>>> commit to Jira first to give others the chance to review and possibly vote
>>> against the patch. Keep in mind that it is our main intention to keep the
>>> branch as stable as possible.
>>> All patches that are intended for the branch should first be committed
>>> to the unstable branch, merged into the stable branch, and then into the
>>> current release branch.
>>> Normal unstable and stable branch development may continue as usual.
>>> However, if you plan to commit a big change to the unstable branch while
>>> the branch feature freeze is in effect, think twice: can't the addition
>>> wait a couple more days? Merges of bug fixes into the branch may become
>>> more difficult.
>>> Only Jira issues with Fix version "6.4" and priority "Blocker" will
>>> delay a release candidate build.
>>>
>>> Thanks,
>>> Jim
>>>
>>
>> --
>> Uwe Schindler
>> Achterdiek 19, 28357 Bremen
>> https://www.thetaphi.de
>>
>
>
Re: 6.4 release
Posted by jim ferenczi <ji...@gmail.com>.
Thanks Uwe !
2017-01-14 16:01 GMT+01:00 Uwe Schindler <uw...@thetaphi.de>:
> Hi Jim,
>
> Thanks! I will update Jenkins this evening (Policeman and ASF).
>
> The first successful Java 9 build 152 was executed already on branch-6x,
> so we are in good shape also on Java 9 front. 😎
>
> Uwe
>
>
> Am 14. Januar 2017 15:57:13 MEZ schrieb jim ferenczi <
> jim.ferenczi@gmail.com>:
>>
>> Hi,
>>
>> The release branch for 6.4 is pushed so the feature freeze phase has
>> officially started.
>> I don't have an admin account on Jenkins so any help would be
>> appreciated. We need to copy the job for the new branch.
>>
>> No new features may be committed to the branch.
>> Documentation patches, build patches and serious bug fixes may be
>> committed to the branch. However, you should submit all patches you want to
>> commit to Jira first to give others the chance to review and possibly vote
>> against the patch. Keep in mind that it is our main intention to keep the
>> branch as stable as possible.
>> All patches that are intended for the branch should first be committed to
>> the unstable branch, merged into the stable branch, and then into the
>> current release branch.
>> Normal unstable and stable branch development may continue as usual.
>> However, if you plan to commit a big change to the unstable branch while
>> the branch feature freeze is in effect, think twice: can't the addition
>> wait a couple more days? Merges of bug fixes into the branch may become
>> more difficult.
>> Only Jira issues with Fix version "6.4" and priority "Blocker" will delay
>> a release candidate build.
>>
>> Thanks,
>> Jim
>>
>
> --
> Uwe Schindler
> Achterdiek 19, 28357 Bremen
> https://www.thetaphi.de
>
Re: 6.4 release
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi Jim,
Thanks! I will update Jenkins this evening (Policeman and ASF).
The first successful Java 9 build 152 was executed already on branch-6x, so we are in good shape also on Java 9 front. 😎
Uwe
Am 14. Januar 2017 15:57:13 MEZ schrieb jim ferenczi <ji...@gmail.com>:
>Hi,
>
>The release branch for 6.4 is pushed so the feature freeze phase has
>officially started.
>I don't have an admin account on Jenkins so any help would be
>appreciated.
>We need to copy the job for the new branch.
>
>No new features may be committed to the branch.
>Documentation patches, build patches and serious bug fixes may be
>committed
>to the branch. However, you should submit all patches you want to
>commit to
>Jira first to give others the chance to review and possibly vote
>against
>the patch. Keep in mind that it is our main intention to keep the
>branch as
>stable as possible.
>All patches that are intended for the branch should first be committed
>to
>the unstable branch, merged into the stable branch, and then into the
>current release branch.
>Normal unstable and stable branch development may continue as usual.
>However, if you plan to commit a big change to the unstable branch
>while
>the branch feature freeze is in effect, think twice: can't the addition
>wait a couple more days? Merges of bug fixes into the branch may become
>more difficult.
>Only Jira issues with Fix version "6.4" and priority "Blocker" will
>delay a
>release candidate build.
>
>Thanks,
>Jim
--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de
RE: 6.4 release
Posted by Uwe Schindler <uw...@thetaphi.de>.
Oh yeah,
please fix! The Jenkins failures are annoying. Is there an issue about that?
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: uwe@thetaphi.de
From: Alan Woodward [mailto:alan@flax.co.uk]
Sent: Monday, January 16, 2017 3:58 PM
To: dev@lucene.apache.org
Subject: Re: 6.4 release
There’s a small bug fix on SOLR-9906 I’d like to push, which should address the frequent failures in PeerSyncReplicationTest we’re seeing.
Alan Woodward
www.flax.co.uk <http://www.flax.co.uk>
On 14 Jan 2017, at 14:57, jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com> > wrote:
Hi,
The release branch for 6.4 is pushed so the feature freeze phase has officially started.
I don't have an admin account on Jenkins so any help would be appreciated. We need to copy the job for the new branch.
No new features may be committed to the branch.
Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
Only Jira issues with Fix version "6.4" and priority "Blocker" will delay a release candidate build.
Thanks,
Jim
Re: 6.4 release
Posted by jim ferenczi <ji...@gmail.com>.
You can still push bug fixes Alan, I'll create the first RC tomorrow if the
all the builds are green.This will let some time for your patch to be
tested.
2017-01-16 15:57 GMT+01:00 Alan Woodward <al...@flax.co.uk>:
> There’s a small bug fix on SOLR-9906 I’d like to push, which should
> address the frequent failures in PeerSyncReplicationTest we’re seeing.
>
> Alan Woodward
> www.flax.co.uk
>
>
> On 14 Jan 2017, at 14:57, jim ferenczi <ji...@gmail.com> wrote:
>
> Hi,
>
> The release branch for 6.4 is pushed so the feature freeze phase has
> officially started.
> I don't have an admin account on Jenkins so any help would be appreciated.
> We need to copy the job for the new branch.
>
> No new features may be committed to the branch.
> Documentation patches, build patches and serious bug fixes may be
> committed to the branch. However, you should submit all patches you want to
> commit to Jira first to give others the chance to review and possibly vote
> against the patch. Keep in mind that it is our main intention to keep the
> branch as stable as possible.
> All patches that are intended for the branch should first be committed to
> the unstable branch, merged into the stable branch, and then into the
> current release branch.
> Normal unstable and stable branch development may continue as usual.
> However, if you plan to commit a big change to the unstable branch while
> the branch feature freeze is in effect, think twice: can't the addition
> wait a couple more days? Merges of bug fixes into the branch may become
> more difficult.
> Only Jira issues with Fix version "6.4" and priority "Blocker" will delay
> a release candidate build.
>
> Thanks,
> Jim
>
>
>
Re: 6.4 release
Posted by Alan Woodward <al...@flax.co.uk>.
There’s a small bug fix on SOLR-9906 I’d like to push, which should address the frequent failures in PeerSyncReplicationTest we’re seeing.
Alan Woodward
www.flax.co.uk
> On 14 Jan 2017, at 14:57, jim ferenczi <ji...@gmail.com> wrote:
>
> Hi,
>
> The release branch for 6.4 is pushed so the feature freeze phase has officially started.
> I don't have an admin account on Jenkins so any help would be appreciated. We need to copy the job for the new branch.
>
> No new features may be committed to the branch.
> Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
> All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
> Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
> Only Jira issues with Fix version "6.4" and priority "Blocker" will delay a release candidate build.
>
> Thanks,
> Jim
Re: 6.4 release
Posted by jim ferenczi <ji...@gmail.com>.
Hi,
The release branch for 6.4 is pushed so the feature freeze phase has
officially started.
I don't have an admin account on Jenkins so any help would be appreciated.
We need to copy the job for the new branch.
No new features may be committed to the branch.
Documentation patches, build patches and serious bug fixes may be committed
to the branch. However, you should submit all patches you want to commit to
Jira first to give others the chance to review and possibly vote against
the patch. Keep in mind that it is our main intention to keep the branch as
stable as possible.
All patches that are intended for the branch should first be committed to
the unstable branch, merged into the stable branch, and then into the
current release branch.
Normal unstable and stable branch development may continue as usual.
However, if you plan to commit a big change to the unstable branch while
the branch feature freeze is in effect, think twice: can't the addition
wait a couple more days? Merges of bug fixes into the branch may become
more difficult.
Only Jira issues with Fix version "6.4" and priority "Blocker" will delay a
release candidate build.
Thanks,
Jim
Re: 6.4 release
Posted by Alan Woodward <al...@flax.co.uk>.
Done!
> On 14 Jan 2017, at 09:39, Alan Woodward <al...@flax.co.uk> wrote:
>
> Hi Jim,
>
> I’d like to land LUCENE-7627 and LUCENE-7628 before you cut the branch - will commit in the next couple of hours assuming all tests run.
>
> Thanks, Alan
>
>
>> On 13 Jan 2017, at 19:46, jim ferenczi <jim.ferenczi@gmail.com <ma...@gmail.com>> wrote:
>>
>> Great news Uwe! I'll cut the branch this week end if nobody disagree.
>>
>> Le 13 janv. 2017 20:24, "Uwe Schindler" <uwe@thetaphi.de <ma...@thetaphi.de>> a écrit :
>> Hi Jim,
>>
>>
>>
>> I updated Groovy. I’d like to run Solr tests this evening through Jenkins with Java 9 EA build 151 to get a list of all tests that have to be disabled for Java 9, but otherwise we are ready.
>>
>>
>>
>> Uwe
>>
>>
>>
>> -----
>>
>> Uwe Schindler
>>
>> Achterdiek 19, D-28357 Bremen
>>
>> http://www.thetaphi.de <http://www.thetaphi.de/>
>> eMail: uwe@thetaphi.de <ma...@thetaphi.de>
>>
>>
>> From: jim ferenczi [mailto:jim.ferenczi@gmail.com <ma...@gmail.com>]
>> Sent: Monday, January 9, 2017 12:37 PM
>> To: dev@lucene.apache.org <ma...@lucene.apache.org>
>> Subject: Re: 6.4 release
>>
>>
>>
>> Thanks for sharing Uwe. It would be wonderful to make latest java9 works with the released version. I can delay the branching until https://issues.apache.org/jira/browse/LUCENE-7596 <https://issues.apache.org/jira/browse/LUCENE-7596> is closed ?
>>
>> In the mean time I am trying to create the release notes in the wiki but I don't have the permissions to create the pages. Where can I get such permissions ?
>>
>>
>>
>> 2017-01-09 11:13 GMT+01:00 Uwe Schindler <uwe@thetaphi.de <ma...@thetaphi.de>>:
>>
>> Hi,
>>
>>
>>
>> I am fine with the start of release process, but I would like to add one thing:
>>
>>
>>
>> I know that Elasticsearch wants to be compatible with recent Java 9 for the continuous delievery process. The new Lucene release is compatible with that (mmap unmapping works), but you cannot build the release with Java 9 148+. Currently the release vote of Groovy 2.4.8 is ongoing and should finish the next few days. So I’d suggest to delay a bit, so I can update common-build.xml and raise the Groovy version: https://issues.apache.org/jira/browse/LUCENE-7596 <https://issues.apache.org/jira/browse/LUCENE-7596>
>>
>>
>> This does not make Solr Tests work with Java 9, but that’s a different discussion (mocking frameworks broke with recent Java 9): https://issues.apache.org/jira/browse/SOLR-9893 <https://issues.apache.org/jira/browse/SOLR-9893>
>> I will fix this by disabling those tests with Java 9, but that a bit of work to set those assumeFalse(Constants.JAVA9….). I don’t see this as a blocker!
>>
>>
>>
>> Uwe
>>
>>
>>
>> -----
>>
>> Uwe Schindler
>>
>> Achterdiek 19, D-28357 Bremen
>>
>> http://www.thetaphi.de <http://www.thetaphi.de/>
>> eMail: uwe@thetaphi.de <ma...@thetaphi.de>
>>
>>
>> From: jim ferenczi [mailto:jim.ferenczi@gmail.com <ma...@gmail.com>]
>> Sent: Tuesday, January 3, 2017 5:23 PM
>> To: dev@lucene.apache.org <ma...@lucene.apache.org>
>> Subject: 6.4 release
>>
>>
>>
>> Hi,
>> I would like to volunteer to release 6.4. I can cut the release branch next Monday if everybody agrees.
>>
>>
>>
>> Jim
>>
>>
>>
>
Re: 6.4 release
Posted by Adrien Grand <jp...@gmail.com>.
Thanks Alan, I just reverted so that this change will first be available in
6.5 and we have more time to sort details out.
I'm happy with the current state of things for getting 6.4 out now.
Le lun. 16 janv. 2017 à 10:42, Alan Woodward <al...@flax.co.uk> a écrit :
> Notifications are back for me as well, must have been a blip.
>
> Feel free to revert the TermsQuery refactor if there are more changes you
> want to add, it’s not vital that it gets out in this release.
>
> Alan Woodward
> www.flax.co.uk
>
>
> On 15 Jan 2017, at 14:43, Adrien Grand <jp...@gmail.com> wrote:
>
> Thanks Alan. Should we do the same with the TermsQuery change since
> whether or not it should accept terms from multiple fields is still under
> discussion?
>
> JIRA notifications are working well for me.
>
> Le dim. 15 janv. 2017 à 10:38, Alan Woodward <al...@flax.co.uk> a écrit :
>
> Sure, I’ll revert it this morning.
>
> As an aside, I don’t seem to be getting email notifications from JIRA
> anymore - is this affecting anybody else?
>
> Alan Woodward
> www.flax.co.uk
>
>
> On 14 Jan 2017, at 21:21, Adrien Grand <jp...@gmail.com> wrote:
>
> Le sam. 14 janv. 2017 à 10:39, Alan Woodward <al...@flax.co.uk> a écrit :
>
> I’d like to land LUCENE-7627 and LUCENE-7628 before you cut the branch -
> will commit in the next couple of hours assuming all tests run.
>
>
> LUCENE-7628 feels a bit rushed in to me. Can we revert from the 6.4 branch
> to have a bit more time to discuss it?
>
>
>
>
Re: 6.4 release
Posted by Alan Woodward <al...@flax.co.uk>.
Notifications are back for me as well, must have been a blip.
Feel free to revert the TermsQuery refactor if there are more changes you want to add, it’s not vital that it gets out in this release.
Alan Woodward
www.flax.co.uk
> On 15 Jan 2017, at 14:43, Adrien Grand <jp...@gmail.com> wrote:
>
> Thanks Alan. Should we do the same with the TermsQuery change since whether or not it should accept terms from multiple fields is still under discussion?
>
> JIRA notifications are working well for me.
>
> Le dim. 15 janv. 2017 à 10:38, Alan Woodward <alan@flax.co.uk <ma...@flax.co.uk>> a écrit :
> Sure, I’ll revert it this morning.
>
> As an aside, I don’t seem to be getting email notifications from JIRA anymore - is this affecting anybody else?
>
> Alan Woodward
> www.flax.co.uk <http://www.flax.co.uk/>
>
>
>> On 14 Jan 2017, at 21:21, Adrien Grand <jpountz@gmail.com <ma...@gmail.com>> wrote:
>>
>> Le sam. 14 janv. 2017 à 10:39, Alan Woodward <alan@flax.co.uk <ma...@flax.co.uk>> a écrit :
>> I’d like to land LUCENE-7627 and LUCENE-7628 before you cut the branch - will commit in the next couple of hours assuming all tests run.
>>
>> LUCENE-7628 feels a bit rushed in to me. Can we revert from the 6.4 branch to have a bit more time to discuss it?
>
Re: 6.4 release
Posted by Adrien Grand <jp...@gmail.com>.
Thanks Alan. Should we do the same with the TermsQuery change since whether
or not it should accept terms from multiple fields is still under
discussion?
JIRA notifications are working well for me.
Le dim. 15 janv. 2017 à 10:38, Alan Woodward <al...@flax.co.uk> a écrit :
> Sure, I’ll revert it this morning.
>
> As an aside, I don’t seem to be getting email notifications from JIRA
> anymore - is this affecting anybody else?
>
> Alan Woodward
> www.flax.co.uk
>
>
> On 14 Jan 2017, at 21:21, Adrien Grand <jp...@gmail.com> wrote:
>
> Le sam. 14 janv. 2017 à 10:39, Alan Woodward <al...@flax.co.uk> a écrit :
>
> I’d like to land LUCENE-7627 and LUCENE-7628 before you cut the branch -
> will commit in the next couple of hours assuming all tests run.
>
>
> LUCENE-7628 feels a bit rushed in to me. Can we revert from the 6.4 branch
> to have a bit more time to discuss it?
>
>
>
Re: 6.4 release
Posted by Alan Woodward <al...@flax.co.uk>.
Sure, I’ll revert it this morning.
As an aside, I don’t seem to be getting email notifications from JIRA anymore - is this affecting anybody else?
Alan Woodward
www.flax.co.uk
> On 14 Jan 2017, at 21:21, Adrien Grand <jp...@gmail.com> wrote:
>
> Le sam. 14 janv. 2017 à 10:39, Alan Woodward <alan@flax.co.uk <ma...@flax.co.uk>> a écrit :
> I’d like to land LUCENE-7627 and LUCENE-7628 before you cut the branch - will commit in the next couple of hours assuming all tests run.
>
> LUCENE-7628 feels a bit rushed in to me. Can we revert from the 6.4 branch to have a bit more time to discuss it?
Re: 6.4 release
Posted by Adrien Grand <jp...@gmail.com>.
Le sam. 14 janv. 2017 à 10:39, Alan Woodward <al...@flax.co.uk> a écrit :
> I’d like to land LUCENE-7627 and LUCENE-7628 before you cut the branch -
> will commit in the next couple of hours assuming all tests run.
>
LUCENE-7628 feels a bit rushed in to me. Can we revert from the 6.4 branch
to have a bit more time to discuss it?
Re: 6.4 release
Posted by Alan Woodward <al...@flax.co.uk>.
Hi Jim,
I’d like to land LUCENE-7627 and LUCENE-7628 before you cut the branch - will commit in the next couple of hours assuming all tests run.
Thanks, Alan
> On 13 Jan 2017, at 19:46, jim ferenczi <ji...@gmail.com> wrote:
>
> Great news Uwe! I'll cut the branch this week end if nobody disagree.
>
> Le 13 janv. 2017 20:24, "Uwe Schindler" <uwe@thetaphi.de <ma...@thetaphi.de>> a écrit :
> Hi Jim,
>
>
>
> I updated Groovy. I’d like to run Solr tests this evening through Jenkins with Java 9 EA build 151 to get a list of all tests that have to be disabled for Java 9, but otherwise we are ready.
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> Achterdiek 19, D-28357 Bremen
>
> http://www.thetaphi.de <http://www.thetaphi.de/>
> eMail: uwe@thetaphi.de <ma...@thetaphi.de>
>
>
> From: jim ferenczi [mailto:jim.ferenczi@gmail.com <ma...@gmail.com>]
> Sent: Monday, January 9, 2017 12:37 PM
> To: dev@lucene.apache.org <ma...@lucene.apache.org>
> Subject: Re: 6.4 release
>
>
>
> Thanks for sharing Uwe. It would be wonderful to make latest java9 works with the released version. I can delay the branching until https://issues.apache.org/jira/browse/LUCENE-7596 <https://issues.apache.org/jira/browse/LUCENE-7596> is closed ?
>
> In the mean time I am trying to create the release notes in the wiki but I don't have the permissions to create the pages. Where can I get such permissions ?
>
>
>
> 2017-01-09 11:13 GMT+01:00 Uwe Schindler <uwe@thetaphi.de <ma...@thetaphi.de>>:
>
> Hi,
>
>
>
> I am fine with the start of release process, but I would like to add one thing:
>
>
>
> I know that Elasticsearch wants to be compatible with recent Java 9 for the continuous delievery process. The new Lucene release is compatible with that (mmap unmapping works), but you cannot build the release with Java 9 148+. Currently the release vote of Groovy 2.4.8 is ongoing and should finish the next few days. So I’d suggest to delay a bit, so I can update common-build.xml and raise the Groovy version: https://issues.apache.org/jira/browse/LUCENE-7596 <https://issues.apache.org/jira/browse/LUCENE-7596>
>
>
> This does not make Solr Tests work with Java 9, but that’s a different discussion (mocking frameworks broke with recent Java 9): https://issues.apache.org/jira/browse/SOLR-9893 <https://issues.apache.org/jira/browse/SOLR-9893>
> I will fix this by disabling those tests with Java 9, but that a bit of work to set those assumeFalse(Constants.JAVA9….). I don’t see this as a blocker!
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> Achterdiek 19, D-28357 Bremen
>
> http://www.thetaphi.de <http://www.thetaphi.de/>
> eMail: uwe@thetaphi.de <ma...@thetaphi.de>
>
>
> From: jim ferenczi [mailto:jim.ferenczi@gmail.com <ma...@gmail.com>]
> Sent: Tuesday, January 3, 2017 5:23 PM
> To: dev@lucene.apache.org <ma...@lucene.apache.org>
> Subject: 6.4 release
>
>
>
> Hi,
> I would like to volunteer to release 6.4. I can cut the release branch next Monday if everybody agrees.
>
>
>
> Jim
>
>
>
RE: 6.4 release
Posted by jim ferenczi <ji...@gmail.com>.
Great news Uwe! I'll cut the branch this week end if nobody disagree.
Le 13 janv. 2017 20:24, "Uwe Schindler" <uw...@thetaphi.de> a écrit :
> Hi Jim,
>
>
>
> I updated Groovy. I’d like to run Solr tests this evening through Jenkins
> with Java 9 EA build 151 to get a list of all tests that have to be
> disabled for Java 9, but otherwise we are ready.
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> Achterdiek 19, D-28357 Bremen
>
> http://www.thetaphi.de
>
> eMail: uwe@thetaphi.de
>
>
>
> *From:* jim ferenczi [mailto:jim.ferenczi@gmail.com]
> *Sent:* Monday, January 9, 2017 12:37 PM
> *To:* dev@lucene.apache.org
> *Subject:* Re: 6.4 release
>
>
>
> Thanks for sharing Uwe. It would be wonderful to make latest java9 works
> with the released version. I can delay the branching until
> https://issues.apache.org/jira/browse/LUCENE-7596 is closed ?
>
> In the mean time I am trying to create the release notes in the wiki but I
> don't have the permissions to create the pages. Where can I get such
> permissions ?
>
>
>
> 2017-01-09 11:13 GMT+01:00 Uwe Schindler <uw...@thetaphi.de>:
>
> Hi,
>
>
>
> I am fine with the start of release process, but I would like to add one
> thing:
>
>
>
> I know that Elasticsearch wants to be compatible with recent Java 9 for
> the continuous delievery process. The new Lucene release is compatible with
> that (mmap unmapping works), but you cannot build the release with Java 9
> 148+. Currently the release vote of Groovy 2.4.8 is ongoing and should
> finish the next few days. So I’d suggest to delay a bit, so I can update
> common-build.xml and raise the Groovy version: https://issues.apache.org/
> jira/browse/LUCENE-7596
>
>
>
> This does not make Solr Tests work with Java 9, but that’s a different
> discussion (mocking frameworks broke with recent Java 9):
> https://issues.apache.org/jira/browse/SOLR-9893
>
> I will fix this by disabling those tests with Java 9, but that a bit of
> work to set those assumeFalse(Constants.JAVA9….). I don’t see this as a
> blocker!
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> Achterdiek 19, D-28357 Bremen
>
> http://www.thetaphi.de
>
> eMail: uwe@thetaphi.de
>
>
>
> *From:* jim ferenczi [mailto:jim.ferenczi@gmail.com]
> *Sent:* Tuesday, January 3, 2017 5:23 PM
> *To:* dev@lucene.apache.org
> *Subject:* 6.4 release
>
>
>
> Hi,
> I would like to volunteer to release 6.4. I can cut the release branch
> next Monday if everybody agrees.
>
>
>
> Jim
>
>
>
RE: 6.4 release
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi Jim,
I updated Groovy. I’d like to run Solr tests this evening through Jenkins with Java 9 EA build 151 to get a list of all tests that have to be disabled for Java 9, but otherwise we are ready.
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: uwe@thetaphi.de
From: jim ferenczi [mailto:jim.ferenczi@gmail.com]
Sent: Monday, January 9, 2017 12:37 PM
To: dev@lucene.apache.org
Subject: Re: 6.4 release
Thanks for sharing Uwe. It would be wonderful to make latest java9 works with the released version. I can delay the branching until https://issues.apache.org/jira/browse/LUCENE-7596 is closed ?
In the mean time I am trying to create the release notes in the wiki but I don't have the permissions to create the pages. Where can I get such permissions ?
2017-01-09 11:13 GMT+01:00 Uwe Schindler <uwe@thetaphi.de <ma...@thetaphi.de> >:
Hi,
I am fine with the start of release process, but I would like to add one thing:
I know that Elasticsearch wants to be compatible with recent Java 9 for the continuous delievery process. The new Lucene release is compatible with that (mmap unmapping works), but you cannot build the release with Java 9 148+. Currently the release vote of Groovy 2.4.8 is ongoing and should finish the next few days. So I’d suggest to delay a bit, so I can update common-build.xml and raise the Groovy version: https://issues.apache.org/jira/browse/LUCENE-7596
This does not make Solr Tests work with Java 9, but that’s a different discussion (mocking frameworks broke with recent Java 9): https://issues.apache.org/jira/browse/SOLR-9893
I will fix this by disabling those tests with Java 9, but that a bit of work to set those assumeFalse(Constants.JAVA9….). I don’t see this as a blocker!
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: uwe@thetaphi.de <ma...@thetaphi.de>
From: jim ferenczi [mailto:jim.ferenczi@gmail.com <ma...@gmail.com> ]
Sent: Tuesday, January 3, 2017 5:23 PM
To: dev@lucene.apache.org <ma...@lucene.apache.org>
Subject: 6.4 release
Hi,
I would like to volunteer to release 6.4. I can cut the release branch next Monday if everybody agrees.
Jim
Re: 6.4 release
Posted by jim ferenczi <ji...@gmail.com>.
Thanks for sharing Uwe. It would be wonderful to make latest java9 works
with the released version. I can delay the branching until
https://issues.apache.org/jira/browse/LUCENE-7596 is closed ?
In the mean time I am trying to create the release notes in the wiki but I
don't have the permissions to create the pages. Where can I get such
permissions ?
2017-01-09 11:13 GMT+01:00 Uwe Schindler <uw...@thetaphi.de>:
> Hi,
>
>
>
> I am fine with the start of release process, but I would like to add one
> thing:
>
>
>
> I know that Elasticsearch wants to be compatible with recent Java 9 for
> the continuous delievery process. The new Lucene release is compatible with
> that (mmap unmapping works), but you cannot build the release with Java 9
> 148+. Currently the release vote of Groovy 2.4.8 is ongoing and should
> finish the next few days. So I’d suggest to delay a bit, so I can update
> common-build.xml and raise the Groovy version: https://issues.apache.org/
> jira/browse/LUCENE-7596
>
>
>
> This does not make Solr Tests work with Java 9, but that’s a different
> discussion (mocking frameworks broke with recent Java 9):
> https://issues.apache.org/jira/browse/SOLR-9893
>
> I will fix this by disabling those tests with Java 9, but that a bit of
> work to set those assumeFalse(Constants.JAVA9….). I don’t see this as a
> blocker!
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> Achterdiek 19, D-28357 Bremen
>
> http://www.thetaphi.de
>
> eMail: uwe@thetaphi.de
>
>
>
> *From:* jim ferenczi [mailto:jim.ferenczi@gmail.com]
> *Sent:* Tuesday, January 3, 2017 5:23 PM
> *To:* dev@lucene.apache.org
> *Subject:* 6.4 release
>
>
>
> Hi,
> I would like to volunteer to release 6.4. I can cut the release branch
> next Monday if everybody agrees.
>
>
>
> Jim
>
RE: 6.4 release
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
I am fine with the start of release process, but I would like to add one thing:
I know that Elasticsearch wants to be compatible with recent Java 9 for the continuous delievery process. The new Lucene release is compatible with that (mmap unmapping works), but you cannot build the release with Java 9 148+. Currently the release vote of Groovy 2.4.8 is ongoing and should finish the next few days. So I’d suggest to delay a bit, so I can update common-build.xml and raise the Groovy version: https://issues.apache.org/jira/browse/LUCENE-7596
This does not make Solr Tests work with Java 9, but that’s a different discussion (mocking frameworks broke with recent Java 9): https://issues.apache.org/jira/browse/SOLR-9893
I will fix this by disabling those tests with Java 9, but that a bit of work to set those assumeFalse(Constants.JAVA9….). I don’t see this as a blocker!
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
<http://www.thetaphi.de/> http://www.thetaphi.de
eMail: uwe@thetaphi.de
From: jim ferenczi [mailto:jim.ferenczi@gmail.com]
Sent: Tuesday, January 3, 2017 5:23 PM
To: dev@lucene.apache.org
Subject: 6.4 release
Hi,
I would like to volunteer to release 6.4. I can cut the release branch next Monday if everybody agrees.
Jim