Hi Christian, These look like great improvements to Kuromoji, but for the same reasons, I think it's risky to commit these changes at the last minute, not giving Jenkins time to chew on it, etc.
I think they should just go into 6.0 instead, which is coming out shortly after 5.5? A release is not the time to shove new features in. Rather, it's the opposite: you hold back large changes for the following release. Mike McCandless http://blog.mikemccandless.com On Wed, Feb 10, 2016 at 4:27 AM, Christian Moen <[email protected]> wrote: > Hello, > > I'd like to get LUCENE-6837 and LUCENE-3922 into 5.5. I believe I can have > them merged this week. > > Best, > Christian > > On Feb 5, 2016, at 02:42, Nicholas Knize <[email protected]> wrote: > > +1 for 5.5.0 release. I have 2 issues I'd like to get in for 5.5: > LUCENE-6930 and LUCENE-6997 which changes GeoPoint encoding (boosting > performance), and graduates these features from sandbox. They should be > ready by Monday (or sooner). > > On Thu, Feb 4, 2016 at 11:00 AM, Michael McCandless > <[email protected]> wrote: >> >> I think we are in good shape now for 6.0.0? >> >> git cutover is done and seems to be going well except for how we name >> branches >> >> Dimensional values are renamed to point values, the API is cleaned up >> a bit, and you can now search for == (not just ranges), and >> StoredDocument is removed. >> >> We should first do a 5.5.0 release to get all the goodness back-ported >> 5.x features out, and also smoke-test our first git-based release. >> Does anyone want to volunteer as RM? >> >> Mike McCandless >> >> http://blog.mikemccandless.com >> >> On Fri, Jan 8, 2016 at 8:24 PM, Mark Miller <[email protected]> wrote: >> > On Fri, Jan 8, 2016 at 2:52 PM Michael McCandless >> > <[email protected]> wrote: >> >> >> >> I agree it would be nice to have cutover to git by then: are we ready >> >> to open an INFRA issue to do the hard cutover? Or do we still have >> >> things to do on our end? (Thank you Dawid and Mark and Paul and Uwe >> >> and everyone else for pushing hard on this front!). >> > >> > >> > We are fairly close - just one last thing to come to consensus on. >> > Remains >> > to be seen how fast INFRA reacts for us though. >> > >> > There will also probably be a bit to do as we work through the first >> > release, in terms of release scripts, docs, etc. I think most of it >> > should >> > be fairly light weight changes though. >> > >> > - Mark >> > -- >> > - Mark >> > about.me/markrmiller >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
