[
https://issues.apache.org/jira/browse/LUCENE-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139054#comment-14139054
]
Uwe Schindler commented on LUCENE-5944:
---------------------------------------
Hi,
there is still a release 4.10.1 underway (Mike will just commit one more issue
soon). In general there is no problem in releasing 4.10.2 quite soon, too.
The fact we agreed on was to move to a new backwards model, because the current
model prevents us from working effectively. So I don't see a 4.11 release
coming anymore. Robert and I added a lot of news for a coming 5.0, which we
will hopefully start as RC quite soon (after a few weeks of fine-tuning). The
new version will still be able to read 4.x indexes, but 3.x gets removed.
The branch_4x branch was removed because commit to 4.x should now only go
through 4.10 branch and all work for 5.0 will go to branch_5x. The whole thing
was just a "rename" of branch. Both branches coexisted for a short time to be
able to get Jenkins servers up-to-date.
> 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
