Changes as we approach v4

["david.w.smiley@gmail.com" <da...@gmail.com>]

Rob,
  It appears you are in-effect the Release Manager for v4.0 so I'm
asking you this question.  Clearly v4 is going to be out soon and
consequently we're not pushing new features to the v4 branch.
Regarding the new spatial codebase, there isn't a backwards
compatibility concern to changes until v4 is actually released.  In
your opinion, is it too late to do class renames in this area? --
LUCENE-4374 is about renaming TwoDoublesStrategy to
PointVectorStrategy (much better name; the old name is crap and that's
my fault).   And FYI I intend to add a bunch of javadocs to all
spatial classes this weekend.

Thanks for all the time you spend on doing your R.M. duties -- it's a
ton of work that few people would step forward to do.

~ David

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org

Re: Changes as we approach v4

["Smiley, David W." <ds...@mitre.org>]

On Sep 21, 2012, at 4:51 PM, Robert Muir wrote:

> On Fri, Sep 21, 2012 at 4:20 PM, david.w.smiley@gmail.com
> <da...@gmail.com> wrote:
>> compatibility concern to changes until v4 is actually released.  In
>> your opinion, is it too late to do class renames in this area? --
>> LUCENE-4374 is about renaming TwoDoublesStrategy to
>> PointVectorStrategy (much better name; the old name is crap and that's
>> my fault).
> 
> I can't really answer this question: as I hinted at monday, I'm not
> going to try to police issues.
> Honestly the codebase is too large for one person to "police" what
> issues go in and out of a release.
> If its something I feel i know pretty well, I'll give my opinion, but
> in general this stuff needs to be decided by the people that know it
> (e.g. you, Chris, Ryan).

Ok good -- makes sense.  In this case I know Chris is a definite fan, and I've given up on trying to contact Ryan these days (never ending vacation?).

> I will only say (not knowing about the classes in question) that there
> is always the conservative option to mark things experimental and
> change them in 4.1.
> Its conservative in the sense that various examples/docs and such wont break.

All Lucene spatial classes have the @lucene.experimental marking already.  I need to add these to the Solr ones too.  I don't want that label to be there always but this technology is moving a bit too fast now.

~ David
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org

Re: Changes as we approach v4

[Robert Muir <rc...@gmail.com>]

On Fri, Sep 21, 2012 at 4:20 PM, david.w.smiley@gmail.com
<da...@gmail.com> wrote:
> compatibility concern to changes until v4 is actually released.  In
> your opinion, is it too late to do class renames in this area? --
> LUCENE-4374 is about renaming TwoDoublesStrategy to
> PointVectorStrategy (much better name; the old name is crap and that's
> my fault).

I can't really answer this question: as I hinted at monday, I'm not
going to try to police issues.
Honestly the codebase is too large for one person to "police" what
issues go in and out of a release.
If its something I feel i know pretty well, I'll give my opinion, but
in general this stuff needs to be decided by the people that know it
(e.g. you, Chris, Ryan).

I will only say (not knowing about the classes in question) that there
is always the conservative option to mark things experimental and
change them in 4.1.
Its conservative in the sense that various examples/docs and such wont break.

> And FYI I intend to add a bunch of javadocs to all
> spatial classes this weekend.
>

+1 this would be really nice. There are a lot of new APIS/changed APIs
in 4.0 and documentation is vital because e.g. people are not going to
be able to go off of Lucene in Action etc.

-- 
lucidworks.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org