Thanks for the clarification! I do indeed recall now that portion of the discussion about renaming of branch_4x to branch_5x with a lot/most of what had previously been trunk, with the most major exception being the trunk war/server changes.
To make the long story short, the next non-patch release of Lucene and Solr will be... 5.0, not 4.11. So, 5.0 should be out, like within the next couple of months. In terms of the impact on anybody for compatibility, the only big thing is that 5.0 will not support 3.x indexes. It will fully support the 4.x indexes though, correct? Will there be any benefit or reason for people to upgrade their 4.x indexes to 5.0? One reason I can think of is so that they will be able to jump from 5.x to 6.0, otherwise 6.0 would refuse to accept their 4.x indexes. Can a 4.x index be easily upgraded to be a 5.x index, like using a utility or optimize? Do I have everything straight now? -- Jack Krupansky From: Ryan Ernst Sent: Saturday, October 4, 2014 3:57 PM To: [email protected] Subject: Re: 5.0 release status? The branch_5x effort is to release what would have been 4.11 as 5.0. The most notable reason being backcompat for 3x indexes, which as Robert has put it is "unmaintainable". AFAICT, there isn’t anything super major in 5x that the world is super-urgently waiting for (WAR vs. server?) The WAR removal was not backported to 5x. It is still on trunk, to be dealt with at a later time. Otherwise, it seems like we can continue to look at an ongoing stream of significant improvements to the 4x branch and that a 5.0 is probably at least a year or so off I don't believe this is correct. The intent here is to have the next release of Lucene be 5.0. Robert has put in a great deal of effort in making improvements in a new Lucene50 codec that were simply not possible on 4x. or simply waiting on some major change that actually warrants a 5.0. There are already some major changes in 5.0: nio2, tons more index corruption protection, super improved debugging for memory allocation of index structures, simpler tokenizer/analyzer interface without Reader, ram usage improvements with the 50 codec work so far. I know I have a list of things I'd like to do API-wise. IMO, a few months, maybe more. On Sat, Oct 4, 2014 at 9:35 AM, Jack Krupansky <[email protected]> wrote: I tried to follow all of the trunk 6/branch 5x discussion, but... AFAICT there was no explicit decision or even implication that a release 5.0 would be imminent or that there would not be a 4.11 release. AFAICT, the whole trunk 6/branch 5x decision was more related to wanting to have a trunk that eliminated the 4x deprecations and was no longer constrained by compatibility with the 4x index – let me know if I am wrong about that in any way! But I did see a comment on one Jira referring to “preparation for a 5.0 release”, so I wanted to inquire about intentions. So, is a 5.0 release “coming soon”, or are 4.11, 4.12, 4.13... equally likely? AFAICT, there isn’t anything super major in 5x that the world is super-urgently waiting for (WAR vs. server?), and people have been really good at making substantial enhancements in the 4x branch, so I would suggest that anybody strongly favoring an imminent 5.0 release (next six months) should make their case more explicitly. Otherwise, it seems like we can continue to look at an ongoing stream of significant improvements to the 4x branch and that a 5.0 is probably at least a year or so off – or simply waiting on some major change that actually warrants a 5.0. Open questions: What is Heliosearch up to, and what are Elasticsearch’s intentions? Comments? -- Jack Krupansky
