My personal preferences on the immediate future are to make Struts 1.2 an evolutionary path for existing 1.0 and 1.1 users, but adopt a "release often" model of 1.2.x releases like what the Apache HTTPD server does, and what Tomcat 4.1 and 5.0 have adopted -- release a new milestone when you've added a new feature or two, or fixed enough bugs to be worthwhile.
(All points taken. I'm wondering if there's a place on Struts website for a "Craig's Column" to host Craig's writings. :-)
Struts' "release cycle/release process" has been a contentious issue. I can't speak for the others, but I believe it's a general feeling among many Struts users that it's more desirable to shorten Struts' beta release cycle. Many developers have constraints implied by their upper managements or clients beta software can't be included in production systems. Adopting a "release often" model is much desired.
Craig McClanahan
--
John Yu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
