[
https://issues.apache.org/jira/browse/LUCENE-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130127#comment-14130127
]
Robert Muir commented on LUCENE-5940:
-------------------------------------
Tim but the "policy" is really a joke. it just locks things in with releases.
Currently if you are on lucene 2, then in order to get to lucene 4, you have to
move to 3.x first.
If we released 5.0 right now, we would not have to deal with 3.x indexes
anymore. We could release 6.0 e.g. within a year of that, and we'd contain the
problem.
I think if i actually proposed 5.0 and took it seriously, no one would really
complain. But its bogus to do this and issue releases with not so many features
just because it makes everyone feel better, when its really the policy that is
broken. That is what we should fix.
This is from someone who has spent the the last 2 days doing nothing but fight
back compat in lucene.
> change index backwards compatibility policy.
> --------------------------------------------
>
> Key: LUCENE-5940
> URL: https://issues.apache.org/jira/browse/LUCENE-5940
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
>
> Currently, our index backwards compatibility is unmanageable. The length of
> time in which we must support old indexes is simply too long.
> The index back compat works like this: everyone wants it, but there are
> frequently bugs, and when push comes to shove, its not a very sexy thing to
> work on/fix, so its hard to get any help.
> Currently our back compat "promise" is just a broken promise, because we
> cannot actually guarantee it for these reasons.
> I propose we scale back the length of time for which we must support old
> indexes.
--
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
