On Tue, Feb 9, 2016 at 3:14 PM, Anshum Gupta <[email protected]> wrote: > Thanks Mike for volunteering!
You're welcome! > I wanted to get SOLR-8619 in for 5.5.0, I'll mark that as a blocker as it > can potentially cause data loss. I'm currently working on that. Hmm this is a little concerning: I don't see a patch on the issue, not even for a test case showing the problem? No comments for the past 1.5 weeks or so? There seems to be a lot of design level discussion there about what the issue(s) are, how to fix it, etc.? It's risky to rush in a fix in just before a release. We can do a 5.5.1 in short order with this fix? Alternatively, we could roll the release bits just for Lucene 5.5.0, and Solr 5.5.0 is released later. > I also have a bunch of Solr related stuff I wanted to commit before moving > on the 6.0 path so back-compat wouldn't be a problem, but we can always have > another deprecation release before 6.0 if needed, specially once we have the > git based release process ironed out. > > I am not saying we WILL have another 5.x release, just a thought. It all > depends on the release timeline for 6.0 :) Hmm, I expect 5.5 will be the last 5.x feature release, i.e. we can do 5.5.x bug fix releases, but I don't think we should do another 5.x feature release once we release 6.0. The next feature release should be 6.1 after that? Or maybe only Solr could do a 5.6.0? Mike McCandless http://blog.mikemccandless.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
