[Zope] 2.3.0 really not Beta?

[Stephan Goeldi]

>I have no such problems.

Nice for you

>Again, 2.3.0 works for me pretty nice in this aspect.
>I am going to switch to VirtualHostMonster, but now I use SiteRoot, and I 
>am satsified.

Do you have different domains under the same tree?
In my installation there are about 10 domains on 1 server.
9 domains work perfect, 1 does not.

>It was declared "stable" exactly because no one caugth such behaviour. In 
>the world of free software it is *you* who test software, send patches to 
>authors, etc. No one ought to do something special for you. Why didn't you 
>test 2.3 betas and caught these errors? Ah, you want only stable software! 
>Then pay for it! Either you must (I said "must") pay with your time (test 
>betas, make patches) or you can pay money.

It doesn't seem to be a good day for you, does it?

Your definition of the word 'stable' seems to be
the Microsoft definition, which doesn't work too.
There I pay for software and it isn't stable anyway.

I don't think that the people of DC think the same
like you. They are interested in a stable and working
Zope, and therefore their support on this list is
professional and perfect. Of course Zope is not
open source only because of philantropic thoughts.

There should not only be the fact, that it is free,
but also the fact, that a declaration of 'stable'
really is trustable.

OK, let's say 2.3.0 is really stable. What is the difference,
which made Zope go away on my redhat server? Is there anything
different in installing 2.3.0 than 2.2.5?

I made the upgrade exactly as described in the Upgrading-Howto.

>Why didn't you test 2.3 betas and caught these errors?

Because I am not a programmer. I am an administrator and
webdesigner. Without this class of users, there would be
no use for Zope. Except for your hobby.





_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.