On Thu, Oct 25, 2012 at 8:52 PM, Mark Miller <[email protected]> wrote: > I think we should start whatever our next release is very soon. > > Given some of the SolrCloud issues, I'd like to do a 4.0.1 personally. But > the issues are not data loss issues, so I could be convinced that 4.1 is > fine. But I feel that means less people will move quickly from 4.0 in that > case, and I don't like it.
Again I disagree, but I'll make my argument mainly from a release engineering perspective. Its simple: 4.1 exists today, jenkins is kicking the shit out of it, if we made a good RC it could maybe even pass. 4.0.1 does not yet exist!, i dont really see bugfixes backported to lucene_solr_4_0_0 branch. If we made a flurry of backports, this would likely create bugs that 4.1 doesnt have. so 4.1 will be a more stable, more reliable release for these reasons. It has nothing to do with how important bugs are or anything. creating a 4.0.1 from scratch is work that i'm not interested in doing (even as a bugfixer backporting bugs i have fixed, 4.1 is a more efficient investment here). > > I'm willing to pitch in on the release process. I don't know that I have the > time (ApacheCon is coming up among other things) to do all of the work - but > I'm happy to co-release-manage with anyone else willing to join in on a 4.0.1 > and/or 4.1 effort. I've love to see something come out in the first half of > Nov. With ApacheCon, that probably means starting sooner rather than later. > I'm busy trying to wrap up any important SolrCloud bug fixes. > I can help with a 4.1 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
