Correction: 3.x is the stable branch, which means it gets both new
features (as long as they are not "disruptive"), as well as bug fixes.

So eg the next stable release is 3.1.  Then 3.1.1, 3.1.2, etc. will be
bug-fix only releases, off of it.  Each 3.x is free to get new
features.

Trunk isn't really a "research project".  Instead, it gets the
features that are too big/risky/disruptive for the stable branch.
It's in fact quite "stable", except, APIs and index format are allowed
to suddenly change, which gives the devs more freedom to make major
improvements to Lucene, like flexible indexing (NOTE: I'm giving a
talk about flexible indexing at Lucene Revolution in Boston, next
week).

The real "research projects" happen on branches, eg the real-time
branch, [soon] the column-stride fields branch, etc.  Branches are
merged back to trunk once they are deemed stable/safe enough.

Mike

On Fri, Sep 24, 2010 at 10:46 PM, Lance Norskog <[email protected]> wrote:
> My understanding is that the 3.x branch is probably the next Solr release.
> It is intended to be a solid  It generally has bug fixes only and the Lucene
> is just a little bit after the Lucene 3.0 release. The trunk is almost a
> research project in implementing new features and index layouts, and it will
> be in churn for awhile.
>
> Jason Rutherglen wrote:
>>
>> I'm a little bit confused about the difference between the Lucene/Solr
>> 3.x branch and Lucene/Solr trunk.  Is there a page on the Lucene
>> Apache site yet for Lucene/Solr 3.x, linked to from the main page?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to