You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Michael McCandless <lu...@mikemccandless.com> on 2016/02/04 18:00:03 UTC
Re: Lucene/Solr 6.0.0 release
I think we are in good shape now for 6.0.0?
git cutover is done and seems to be going well except for how we name branches
Dimensional values are renamed to point values, the API is cleaned up
a bit, and you can now search for == (not just ranges), and
StoredDocument is removed.
We should first do a 5.5.0 release to get all the goodness back-ported
5.x features out, and also smoke-test our first git-based release.
Does anyone want to volunteer as RM?
Mike McCandless
http://blog.mikemccandless.com
On Fri, Jan 8, 2016 at 8:24 PM, Mark Miller <ma...@gmail.com> wrote:
> On Fri, Jan 8, 2016 at 2:52 PM Michael McCandless
> <lu...@mikemccandless.com> wrote:
>>
>> I agree it would be nice to have cutover to git by then: are we ready
>> to open an INFRA issue to do the hard cutover? Or do we still have
>> things to do on our end? (Thank you Dawid and Mark and Paul and Uwe
>> and everyone else for pushing hard on this front!).
>
>
> We are fairly close - just one last thing to come to consensus on. Remains
> to be seen how fast INFRA reacts for us though.
>
> There will also probably be a bit to do as we work through the first
> release, in terms of release scripts, docs, etc. I think most of it should
> be fairly light weight changes though.
>
> - Mark
> --
> - Mark
> about.me/markrmiller
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Lucene/Solr 6.0.0 release
Posted by Michael McCandless <lu...@mikemccandless.com>.
Hi Christian,
These look like great improvements to Kuromoji, but for the same
reasons, I think it's risky to commit these changes at the last
minute, not giving Jenkins time to chew on it, etc.
I think they should just go into 6.0 instead, which is coming out
shortly after 5.5?
A release is not the time to shove new features in. Rather, it's the
opposite: you hold back large changes for the following release.
Mike McCandless
http://blog.mikemccandless.com
On Wed, Feb 10, 2016 at 4:27 AM, Christian Moen <cm...@atilika.com> wrote:
> Hello,
>
> I'd like to get LUCENE-6837 and LUCENE-3922 into 5.5. I believe I can have
> them merged this week.
>
> Best,
> Christian
>
> On Feb 5, 2016, at 02:42, Nicholas Knize <nk...@gmail.com> wrote:
>
> +1 for 5.5.0 release. I have 2 issues I'd like to get in for 5.5:
> LUCENE-6930 and LUCENE-6997 which changes GeoPoint encoding (boosting
> performance), and graduates these features from sandbox. They should be
> ready by Monday (or sooner).
>
> On Thu, Feb 4, 2016 at 11:00 AM, Michael McCandless
> <lu...@mikemccandless.com> wrote:
>>
>> I think we are in good shape now for 6.0.0?
>>
>> git cutover is done and seems to be going well except for how we name
>> branches
>>
>> Dimensional values are renamed to point values, the API is cleaned up
>> a bit, and you can now search for == (not just ranges), and
>> StoredDocument is removed.
>>
>> We should first do a 5.5.0 release to get all the goodness back-ported
>> 5.x features out, and also smoke-test our first git-based release.
>> Does anyone want to volunteer as RM?
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>> On Fri, Jan 8, 2016 at 8:24 PM, Mark Miller <ma...@gmail.com> wrote:
>> > On Fri, Jan 8, 2016 at 2:52 PM Michael McCandless
>> > <lu...@mikemccandless.com> wrote:
>> >>
>> >> I agree it would be nice to have cutover to git by then: are we ready
>> >> to open an INFRA issue to do the hard cutover? Or do we still have
>> >> things to do on our end? (Thank you Dawid and Mark and Paul and Uwe
>> >> and everyone else for pushing hard on this front!).
>> >
>> >
>> > We are fairly close - just one last thing to come to consensus on.
>> > Remains
>> > to be seen how fast INFRA reacts for us though.
>> >
>> > There will also probably be a bit to do as we work through the first
>> > release, in terms of release scripts, docs, etc. I think most of it
>> > should
>> > be fairly light weight changes though.
>> >
>> > - Mark
>> > --
>> > - Mark
>> > about.me/markrmiller
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Lucene/Solr 6.0.0 release
Posted by Christian Moen <cm...@atilika.com>.
Hello,
I'd like to get LUCENE-6837 and LUCENE-3922 into 5.5. I believe I can have them merged this week.
Best,
Christian
> On Feb 5, 2016, at 02:42, Nicholas Knize <nk...@gmail.com> wrote:
>
> +1 for 5.5.0 release. I have 2 issues I'd like to get in for 5.5: LUCENE-6930 <https://issues.apache.org/jira/browse/LUCENE-6930> and LUCENE-6997 <https://issues.apache.org/jira/browse/LUCENE-6997> which changes GeoPoint encoding (boosting performance), and graduates these features from sandbox. They should be ready by Monday (or sooner).
>
> On Thu, Feb 4, 2016 at 11:00 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
> I think we are in good shape now for 6.0.0?
>
> git cutover is done and seems to be going well except for how we name branches
>
> Dimensional values are renamed to point values, the API is cleaned up
> a bit, and you can now search for == (not just ranges), and
> StoredDocument is removed.
>
> We should first do a 5.5.0 release to get all the goodness back-ported
> 5.x features out, and also smoke-test our first git-based release.
> Does anyone want to volunteer as RM?
>
> Mike McCandless
>
> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>
> On Fri, Jan 8, 2016 at 8:24 PM, Mark Miller <markrmiller@gmail.com <ma...@gmail.com>> wrote:
> > On Fri, Jan 8, 2016 at 2:52 PM Michael McCandless
> > <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
> >>
> >> I agree it would be nice to have cutover to git by then: are we ready
> >> to open an INFRA issue to do the hard cutover? Or do we still have
> >> things to do on our end? (Thank you Dawid and Mark and Paul and Uwe
> >> and everyone else for pushing hard on this front!).
> >
> >
> > We are fairly close - just one last thing to come to consensus on. Remains
> > to be seen how fast INFRA reacts for us though.
> >
> > There will also probably be a bit to do as we work through the first
> > release, in terms of release scripts, docs, etc. I think most of it should
> > be fairly light weight changes though.
> >
> > - Mark
> > --
> > - Mark
> > about.me/markrmiller <http://about.me/markrmiller>
>
> ---------------------------------------------------------------------
> 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: Lucene/Solr 6.0.0 release
Posted by Michael McCandless <lu...@mikemccandless.com>.
Thanks Nick and Anshum, I'll volunteer to be RM. If there are blocker
5.5 issues, please mark them as such in Jira, thanks!
I don't think we are rushing here ... it was a little under a month
ago when I had thought "in or week or two" let's cut the 6.x branch ;)
I see 5.5 release as just getting all the (stable) backported features
out to the world before we release 6.0.0.
I'll aim to cut the 5.5 branch mid next week...
Mike McCandless
http://blog.mikemccandless.com
On Thu, Feb 4, 2016 at 1:04 PM, Anshum Gupta <an...@anshumgupta.net> wrote:
> I have a few things I'd like to get in. I hope to get those in by next week.
>
> I think the 5.5 release is an important one for us as the cleanup in 6.0
> depends on it. We shouldn't rush it.
>
> On Thu, Feb 4, 2016 at 9:42 AM, Nicholas Knize <nk...@gmail.com> wrote:
>>
>> +1 for 5.5.0 release. I have 2 issues I'd like to get in for 5.5:
>> LUCENE-6930 and LUCENE-6997 which changes GeoPoint encoding (boosting
>> performance), and graduates these features from sandbox. They should be
>> ready by Monday (or sooner).
>>
>> On Thu, Feb 4, 2016 at 11:00 AM, Michael McCandless
>> <lu...@mikemccandless.com> wrote:
>>>
>>> I think we are in good shape now for 6.0.0?
>>>
>>> git cutover is done and seems to be going well except for how we name
>>> branches
>>>
>>> Dimensional values are renamed to point values, the API is cleaned up
>>> a bit, and you can now search for == (not just ranges), and
>>> StoredDocument is removed.
>>>
>>> We should first do a 5.5.0 release to get all the goodness back-ported
>>> 5.x features out, and also smoke-test our first git-based release.
>>> Does anyone want to volunteer as RM?
>>>
>>> Mike McCandless
>>>
>>> http://blog.mikemccandless.com
>>>
>>> On Fri, Jan 8, 2016 at 8:24 PM, Mark Miller <ma...@gmail.com>
>>> wrote:
>>> > On Fri, Jan 8, 2016 at 2:52 PM Michael McCandless
>>> > <lu...@mikemccandless.com> wrote:
>>> >>
>>> >> I agree it would be nice to have cutover to git by then: are we ready
>>> >> to open an INFRA issue to do the hard cutover? Or do we still have
>>> >> things to do on our end? (Thank you Dawid and Mark and Paul and Uwe
>>> >> and everyone else for pushing hard on this front!).
>>> >
>>> >
>>> > We are fairly close - just one last thing to come to consensus on.
>>> > Remains
>>> > to be seen how fast INFRA reacts for us though.
>>> >
>>> > There will also probably be a bit to do as we work through the first
>>> > release, in terms of release scripts, docs, etc. I think most of it
>>> > should
>>> > be fairly light weight changes though.
>>> >
>>> > - Mark
>>> > --
>>> > - Mark
>>> > about.me/markrmiller
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>
>
>
>
> --
> Anshum Gupta
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Lucene/Solr 6.0.0 release
Posted by Anshum Gupta <an...@anshumgupta.net>.
I have a few things I'd like to get in. I hope to get those in by next
week.
I think the 5.5 release is an important one for us as the cleanup in 6.0
depends on it. We shouldn't rush it.
On Thu, Feb 4, 2016 at 9:42 AM, Nicholas Knize <nk...@gmail.com> wrote:
> +1 for 5.5.0 release. I have 2 issues I'd like to get in for 5.5:
> LUCENE-6930 <https://issues.apache.org/jira/browse/LUCENE-6930> and
> LUCENE-6997 <https://issues.apache.org/jira/browse/LUCENE-6997> which
> changes GeoPoint encoding (boosting performance), and graduates these
> features from sandbox. They should be ready by Monday (or sooner).
>
> On Thu, Feb 4, 2016 at 11:00 AM, Michael McCandless <
> lucene@mikemccandless.com> wrote:
>
>> I think we are in good shape now for 6.0.0?
>>
>> git cutover is done and seems to be going well except for how we name
>> branches
>>
>> Dimensional values are renamed to point values, the API is cleaned up
>> a bit, and you can now search for == (not just ranges), and
>> StoredDocument is removed.
>>
>> We should first do a 5.5.0 release to get all the goodness back-ported
>> 5.x features out, and also smoke-test our first git-based release.
>> Does anyone want to volunteer as RM?
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>> On Fri, Jan 8, 2016 at 8:24 PM, Mark Miller <ma...@gmail.com>
>> wrote:
>> > On Fri, Jan 8, 2016 at 2:52 PM Michael McCandless
>> > <lu...@mikemccandless.com> wrote:
>> >>
>> >> I agree it would be nice to have cutover to git by then: are we ready
>> >> to open an INFRA issue to do the hard cutover? Or do we still have
>> >> things to do on our end? (Thank you Dawid and Mark and Paul and Uwe
>> >> and everyone else for pushing hard on this front!).
>> >
>> >
>> > We are fairly close - just one last thing to come to consensus on.
>> Remains
>> > to be seen how fast INFRA reacts for us though.
>> >
>> > There will also probably be a bit to do as we work through the first
>> > release, in terms of release scripts, docs, etc. I think most of it
>> should
>> > be fairly light weight changes though.
>> >
>> > - Mark
>> > --
>> > - Mark
>> > about.me/markrmiller
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
--
Anshum Gupta
Re: Lucene/Solr 6.0.0 release
Posted by Nicholas Knize <nk...@gmail.com>.
+1 for 5.5.0 release. I have 2 issues I'd like to get in for 5.5:
LUCENE-6930 <https://issues.apache.org/jira/browse/LUCENE-6930> and
LUCENE-6997 <https://issues.apache.org/jira/browse/LUCENE-6997> which
changes GeoPoint encoding (boosting performance), and graduates these
features from sandbox. They should be ready by Monday (or sooner).
On Thu, Feb 4, 2016 at 11:00 AM, Michael McCandless <
lucene@mikemccandless.com> wrote:
> I think we are in good shape now for 6.0.0?
>
> git cutover is done and seems to be going well except for how we name
> branches
>
> Dimensional values are renamed to point values, the API is cleaned up
> a bit, and you can now search for == (not just ranges), and
> StoredDocument is removed.
>
> We should first do a 5.5.0 release to get all the goodness back-ported
> 5.x features out, and also smoke-test our first git-based release.
> Does anyone want to volunteer as RM?
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Fri, Jan 8, 2016 at 8:24 PM, Mark Miller <ma...@gmail.com> wrote:
> > On Fri, Jan 8, 2016 at 2:52 PM Michael McCandless
> > <lu...@mikemccandless.com> wrote:
> >>
> >> I agree it would be nice to have cutover to git by then: are we ready
> >> to open an INFRA issue to do the hard cutover? Or do we still have
> >> things to do on our end? (Thank you Dawid and Mark and Paul and Uwe
> >> and everyone else for pushing hard on this front!).
> >
> >
> > We are fairly close - just one last thing to come to consensus on.
> Remains
> > to be seen how fast INFRA reacts for us though.
> >
> > There will also probably be a bit to do as we work through the first
> > release, in terms of release scripts, docs, etc. I think most of it
> should
> > be fairly light weight changes though.
> >
> > - Mark
> > --
> > - Mark
> > about.me/markrmiller
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>