There remains a known performance issue that in our tests effectively quarters Tapestry throughput. Before releasing T4, I'd like to see either a commitment for a timeframe for the release of a fix for HIVEMIND-162, or the simple changes suggested by TAPESTRY-809. Without these, anyone building large scale sites on Tapestry is likely to have to patch to solve the issue.
Jeff Lubetkin: -1 (non-binding) jeff -----Original Message----- From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] Sent: Friday, December 30, 2005 9:09 AM To: Tapestry development Subject: [VOTE] 4.0 final release I think 4.0 is ready for a wider release and a new release announcement to ring in 2006. I know I'm anxious to start putting together 4.1 features. The most critical missing documentation, about validation, has been remedied by Jesse and some irritating bugs have been fixed. Howard M. Lewis Ship: +1 -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
