[
https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139164#comment-14139164
]
Ryan Ernst commented on LUCENE-5944:
------------------------------------
bq. I wonder when would the code in trunk (that already exists, and is
different from 4x (now 5x)) be released.
When 6.0 is released? Part of the reason for this is a lot of very scary
changes that were being backported into 4.11, that should have been in a major
release. Having a tighter backcompat policy in the future (now starting with
6.x I guess) would help us do releases more quickly (IMO, around every year or
a little more). See LUCENE-5940 that Uwe mentioned earlier here. Simply
releasing 5.0 from trunk would have been more controversial (probably) since it
has a lot of changes that still need to be cleaned up
(StoredDocument/IndexedDocument, what happens with solr war/nowar, etc).
> move trunk to 6.x, create branch_5x
> -----------------------------------
>
> Key: LUCENE-5944
> URL: https://issues.apache.org/jira/browse/LUCENE-5944
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Robert Muir
> Fix For: 5.0
>
>
> In order to actually add real features (as opposed to just spending 24/7
> fixing bugs and back compat), I need a trunk that doesn't have the back
> compat handcuffs.
> In the meantime, we should rename the current trunk (which is totally tied
> down in back compat already, without even a single release!) to branch_5x
> while you guys (i wont be doing any back compat anymore) figure out what you
> want to do with the back compat policly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
