> > We did prototyping and testing with V1.3.6, and we are about to start > a project to produce a production system. We would prefer to start > with the "latest" version, and not have to do the upgrade to a newer > during the project or soon after. At this point we are planning on > starting the effort using V2.0b. How would you characterize the > status of the beta? Feature complete (well, not completely, I gather > from your response below)?
It's feature complete (I think TH will not make it into 2.0) > Stable? Yes, we use it in production for all our projects >How much use has it had? >From the questions on the list, it seem that it has already a lot of users. > Is it > close to release? Yes, hopefully the final release will be in one or two month > Would you recommend starting a project with it, or > sticking with the V1.3.6 release? > Use 2.0 and not 1.3.6. With 2.0 you get a lot of features you don't have in 1.3.x and it really ready for use. There are only a few very small issuse that I need to sort out before releasing the final 2.0 version. Gerald -------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh IT-Securitylösungen * dynamische Webapplikationen * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 939-122 WWW: http://www.ecos.de/ Fax: +49 6133 939-333 -------------------------------------------------------------- | | ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info | +------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
