On the RoughSpots page, * http://wiki.apache.org/struts/RoughSpots
there's a reference to Action 3.x that speaks as if it's far away. That doesn't need to be the case. We can create a branch for "Action Next" or "Ti2" as soon as the code comes down from the incubator. We did the same for Action 1.2 and Action 1.3. We've continued to maintain and extend Action 1.2, while more agressive changes where made to Action 1.3. The original proposal was for Ti to happen in two phases. The first phase was to release Action 2.0 based on WebWork 2.2 by making only necessary and prudent changes. More aggressive changes were to happen in Ti Phase 2. Many of the "Rough Spots" may be Phase 2 changes. Phase 2 might be Action 2.1 or Action 3.x. That's a decision we can make later. Personally, I don't believe the release of Action 2.0 is going to create a migration stampede. Some people who are starting new projects may decide to use Action 2 instead of Action 1. But the people I know won't bother to migrate existing applications. At least not anytime soon. Right now, some teams that are looking forward to Action 2 are getting started with WebWork 2.2 now. I suggest that Job One should be to get a current release out there that we can use while we work on Phase 2. Otherwise, we could easily find ourself maintaining WebWork 2.x at OpenSymphony and then having to mirror any changes in Action 2.x at Apache Struts. I think it's important to first create a stable release of Action 2.0 as the direct successor to WebWork 2.2, and then focus on the more aggressive changes slated for Phase 2. We can make it very clear to people that "Phase 2" is in the works, so people who don't want to migrate more than once can make an informed decision. Thoughts? -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
