Unless you need the goodies in 4.x, I'd go with 3.1, just on the principle that 4.x is more fluid than 3.1, and I'd go with more static code. 4.x gets whatever patches the committers decide are good whereas 3.1 (or 3.2 if that comes out) will have a smaller set of changes.
Both are well tested, it's mostly a matter of your risk tolerance. Why take any risk you don't have to? Best Erick On Fri, Apr 8, 2011 at 10:58 AM, Mark <static.void....@gmail.com> wrote: > Doesn't look like you allow new members to post questions in that forum. > > I have just one last question ;) > > We are deciding whether to upgrade our 1.4 production environment to 4.x or > 3.1. What were you decisions when deciding to release 4.x over 3.1? > > Thanks again > > > On 4/8/11 1:13 AM, Andrzej Bialecki wrote: > >> On 4/7/11 10:16 PM, Mark wrote: >> >>> Andrezej, >>> >>> Thanks for the info. I have a question regarding stability though. How >>> are you able to guarantee the stability of this release when 4.0 is >>> still a work in progress? I believe the last version Lucid released was >>> 1.4 so why did you choose to release a 4.x version as opposed to 3.1? >>> >> >> To include all the goodies from 4.0, of course ;) LucidWorks uses a >> version from the trunk that behaves well in tests and with necessary patches >> applied - see also below. >> >> >>> Is the source code including with your distribution so that we may be >>> able to do some further patching upon it? >>> >> >> Yes, after installing it's in solr-src/ . So if any issue pops up you can >> apply a patch, recompile the libs and replace them. >> >> >>> Thanks again and hopefully I'll be joining you at that conference. >>> >> >> Great :) >> >> PS. Questions like this are best asked on the Lucid forum >> http://www.lucidimagination.com/forum/ . >> >>
