On 5/10/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
Once you have had a chance to review this test build, please respond with a vote on its quality: [ ] Alpha [X] Beta [ ] General Availability (GA)
Sorry for the late response - I've been at The Ajax Experience conference for the last couple of days. I'm afraid that the Tiles DTD issue is enough for me to vote (strongly, in fact) against GA. If this release went GA, it would be our first 1.3 GA release, and thus has the potential for being downloaded and used by thousands of Struts developers. To have all of those developers' applications hitting ASF infrastructure every time they start their apps is not tenable. The infrastructure people are already very irritated indeed by all the hits coming from Java applications looking for DTDs, and some have suggested removing the use of DTDs completely if the applications cannot be prevented from hitting ASF infrastructure to verify them. IIRC, 6% of all minotaur traffic is for DTDs, and Struts is already the worst offender, by a significant margin. For us to consciously vote to release 1.3.4 as GA, and thus significantly exacerbate this problem - well, let's just say that if I could veto a 1.3.4 GA release, I would. I understand that there is a great desire to get a GA release out so that it can be announced at JavaOne. I too think this would be great - we really do need to see a 1.3 GA release out the door. But it needs to be GA quality, not just labelled GA in the interest of the timing of the announcement. Unfortunately, while I was out at TAE, my illustrious team managed to break the build of our primary 1.3-based app, so I haven't been able to evaluate 1.3.4 functionally at this point. I'll try to provide further feedback if I can get that resolved first. -- Martin Cooper
