> Good point. Is there a list of known issues with 1.3 (so I > can check if I > need to fix anything before I use it)? One thing is that > there may be a > danger that some "interface" will change from now to release that will > require changes to how we use it -- pre-release software is > often more in a > state of flux and may require more work to keep up. What is > the state of > 1.3? How are people using it?
Yes, you have some good points there. I don't think we could _guarantee_ that an interface might change, but I would think that it is incredibly unlikely at this point. The only foreseeable changes would be additional objects/components or methods. But again, I can't give you that 100% money back guarantee. You can always look at the new things in 1.3 that you are interested in (new Rolling architecture), have a look at the test cases that Ceki has written for them and make an evaluation as to how stable it looks. My vote would be that this area is looking very good. You can then do your own testing, and provide us any feedback. You can even make the fixes and send us the patches from your experience! :) cheers, Paul Smith --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]