Hi Jeff, The 0.11.6 release has only a LITTLE bugfix. Also, closing tickets as "wont fix" is easy. Have a look at the latest MEANINGFUL changesets, long time ago :)
Cheers, Jérémie On Jan 30, 10:19 pm, Jeff <[EMAIL PROTECTED]> wrote: > Are you sure Ferret development has stopped? According to the Ferret > trac, last change to the trunk was only a few weeks ago, and last tag > (0.11.6) was dated Nov 28 2007, only two months ago. I also see the > developer replying to tickets just this month. Am I missing something > here? > > On Jan 30, 3:33 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > Hi Jens, > > > It's been a long time ;) Hope you're doing well. > > I have something to say about that all: Even if you find a right way > > of making Ferret quite *"stable"*, the development has stopped for > > more than a year now, leaving a LOT of bugs unsolved. > > Ferret has no future for the moment, and considering builduing website > > on it's top is like doing extrem sports on a just recovered broken > > leg.. > > > Cheers, > > Jérémie > > > On Jan 25, 5:06 pm, "Jens Krämer" <[EMAIL PROTECTED]> wrote: > > > > Hi! > > > > > Ferret is unstable in production. Segfaults, corrupted indexes > > > > galore. We've switched around 40 clients form ferret to sphinx and > > > > solved their problems this way. I will never use ferret again after > > > > all the problems I have seen it cause peoples production apps. > > > > I'd really like anybody experiencing problems like this to contact me > > > or even > > > better the ferret-talk mailing list about such problems. I have > > > several sites using > > > Ferret with DRb server runs rock solid there. I must admit that > > > they're relatively low > > > traffic, but high load is nothing that will make Ferret crash or > > > currupt indexes, if you > > > use it in the right way (say, one process accessing the index). > > > Without doubt there > > > are cases when Ferret will segfault, i.e. because of platform specific > > > problems, poor > > > argument checking and error handling in the C code and so on, but they > > > may be > > > circumvented most of the time. Not nice, but acts_as_ferret already > > > does most of this > > > for you. > > > > I also did some load tests with acts_as_ferret's DRb server a while > > > ago, where it handled> 30 mixed indexing and search requests per second > > > from multiple client processes for hours, > > > > and no crash or index corruption (index size was 7GB at the end of the > > > run) happened. > > > > So to summarize: it's definitely possible to have a stable Ferret > > > setup, before you take on the > > > work to switch to something else why not drop me a line and I'll be > > > happy to have a look at your > > > problem. > > > > However from what I've read here I'll be sure to check out Sphinx soon > > > so I know what you're > > > talking about here ;-) > > > > Cheers, > > > Jens --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
