> > The problem was mentioned > > I personally reacted and possibly even found and > fixed some of the bugs in 1 day > after that I created test classes and asked people to test > it?(did you try > it???) > sent about 10 mail's about this subject > talked about it with many people > Tell me what more can I do?
Just for your information: At a lot of companies it takes a lot of effort to convince people to use open source products. I believe in open source, I am a big fan of emacs, cvs and linux. I proposed to use mmbase for our project at Vodafone. Due to the fact that this bug in MMBase was the reason for not going in production, this was for some people a good reason to oppose against open source in general. Don't get me wrong, I know what open source means. I also know we should discuss several topics. I just want to make clear that for using mmbase in a professional environment, these kind of messages don't do any good to anyone. > > is the deadlock still there? We are still testing with the fix of Nico, the deadlock seems to be gone. To be sure, we have to test a few days more. > are U using the old or "new" storage classes? We are using the old storage classes. This is not the good time to move to a new, not released and hard-tested version of parts of mmbase. > > what do the logs say when debugging > (MultiPool/MultiConnection/DijkstraaSemaphore) is on? we can probably test this next week, after we go in production. > > > O course "it's a practical joke" to call an old "bug" a feature. > maybe it should have added a ":)". That wouldn't have helped. Maybe I don't have the same sense of humour... > But we are working hard to make it all good > usually we try to keep compatible with older stuff. I think > that part why > new new storage classes where created and the current ones > where not altered. > I will personally keep my focus on the "new Storage" classes > and not any more > on the older ones. If there is a deadlock in the old classes > I have given you > a possible reason why it happens (but i won't fix it) granted. > > If people come on the dev list, they should expect some discussion > a bit of flames and some nonesence > and if you pick that one sentence of one "open-source" > developer that is > really a shame. The rest doesn't deserve it you're right. I didn't blame the rest of the developers. The underlying message from me is that the community needs to become more mature and it wasn't just one sentence. > > greets > grz2
