On 7/24/06, Ted Husted <[EMAIL PROTECTED]> wrote:
It's a gentle slide for WebWork 2.2 developers now, and some of us would like to keep it that way.
It will be gentle either way; there's no reason we can't continue to support the existing API in a deprecated fashion. WebWork teams perhaps, but Struts 1 teams are glacial when it comes to
decisions like this. From my experience, the majority of Struts teams are still using Struts 1.1. If we bring out a stable release now, I would venture that the earliest most teams would consider upgrading is Q1 2007
Let's not confuse users even more by releasing major changes in a short period of time and risk them postponing adoption even longer or not adopting at all. I like Google's slogan: The best is never good enough. I don't think any framework we have today meets our ultimate vision
yet. If we continue to pursue perfection without releasing, we will never achieve perfection.
We're not stalling for perfection. We have concrete goals which happen to not fit a deadline we set long before we knew exactly what we were going to do. We were hard on the August deadline because we wanted to maintain momentum, but I think we have plenty of momentum and desire to get these features in and out. Bob
