There are just a lot of bug fixes, not really anything particularly nasty. I think we will probably do a 4.3 soon as well, but we have not invested time in a point release in a while and I think it causes fewer upgrades that will fix bugs. I think people are less likely to upgrade to 4.3 than 4.2.1 anytime soon. Because of that, and because Robert shouldered most of the 4.2 burden, I figured I could stand to put some effort into a 4.2.1.
Part of this is guilt I suppose? There have been bugs that I have thought warranted a 4.0.1 and 4.1.1, but I never felt I had the time/energy to shoulder a release. There are parts that involve Maven :) One of the more annoying bugs to me is that accessing the admin UI in SolrCloud mode causes lots of warning logging that fills up your logs and looks scary - just that makes me want a 4.2.1, but there are lots of other bugs fixes already as well. - Mark On Mar 17, 2013, at 9:45 PM, Bill Au <[email protected]> wrote: > Mark, thanks for the heads up. As I don't want to go through to upgrade > cycle in such short period, I will skip 4.2.0 and wait for 4.2.1. > > I am curious as to why 4.2.1 so soon. Is there some nasty bug(s) in 4.2.0? > If that's the case I think I would like to know. > > Bill > > > On Sun, Mar 17, 2013 at 8:30 PM, Steve Rowe <[email protected]> wrote: > Done, also added 4.2.1 sections in CHANGES.txt files on trunk and branch_4x. > > I'll backport my issues now: > > * SOLR-4537: Clean up schema information REST API. > * SOLR-4567: copyField source glob matching explicit field(s) stopped working > in Solr 4.2. > > Steve > > On Mar 17, 2013, at 7:51 PM, Steve Rowe <[email protected]> wrote: > > > > > On Mar 17, 2013, at 3:17 PM, Uwe Schindler <[email protected]> wrote: > >> I think the branch should already be setup for 4.2.1, maybe you only need > >> to raise version numbers. > > > > I'll do this. > > > > Steve > > > --------------------------------------------------------------------- > 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]
