>> To me that difference isn't in quality, it is in API >> stability. I agree. The difference between an alpha and a 1.0 release is that when a version number is cut, there is an implication of API stability and maintenance of that API at least until the next major revision. For example, even while Sun was developing JDK 1.1, they were making bug fixes to 1.0. They were maintaining that interface. Even then they maintained that interface in future releases. I think you miss the point. Cocoon has passed a 1.0. Now they are completly changing everything for a 2.0. You could start with Turbine or Cocoon today and have the same exact problem in 3 months when 'everything' looks different. Anyone who looks at the version number and says 'It just isn't ready', should not be using OSS in the first place. IMHO, if jon tells me it is prime-time, then it is. jon runs a business in his 'spare-time' (at least he used to), and if he is using Turbine for that, then I am sure that he is aware of changing APIs and what that menas to a developer using the product. Scott Sanders -- ---------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED]
