Hmm both of those issues are still open / being worked on? I don't think we should rush bug fixes in for point releases, i.e. if we already have a bug fixed in 5.x/trunk and Jenkins has had plenty of time to chew on it, it makes sense to backport.
Unless the fixes are clearly low risk (I can't tell here)... We can always do a 4.10.5 in short order once these fixes have had time to bake... Mike McCandless http://blog.mikemccandless.com On Wed, Feb 25, 2015 at 3:48 AM, Shalin Shekhar Mangar <shalinman...@gmail.com> wrote: > Thanks for volunteering, Mike. I was going to propose a 4.10.4 myself > because of SOLR-7128 which is a very bad performance bug. I am currently > writing better testing tools for such bugs via SOLR-7147. I am quite sure it > that I'll land the fix today but if not, I'd appreciate if you can wait > another day for them. > > I'll back-port some Solr issues to 4.10.4 too. > > On Wed, Feb 25, 2015 at 2:09 PM, Michael McCandless > <luc...@mikemccandless.com> wrote: >> >> We have a number of juicy bug fixes for 4.10.4 already ... I think >> it's time to release it? >> >> I can be RM ... I'll cut an RC tomorrow. >> >> If there are bug fixes you want to backport please go reopen and mark >> as 4.10.4 blocker. >> >> Mike McCandless >> >> http://blog.mikemccandless.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> > > > > -- > Regards, > Shalin Shekhar Mangar. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
