Ted, I think that your statement is one of the things that needs to be discussed. There is the camp that says "The first SAF 2.0 release should have a solid API that will be usable for a long time". The second group says that "The first SAF 2.0 release should basically be WW 2.2 with some minor changes on top of it."
These two statements are not mutually exclusive, but I think different people have different priorities and what the final set of priorities is needs to be hashed out. i.e. Will phase II be a radical upgrade from Phase I that might be called Struts 3? Or are we going to be setting Phase II up with the first release of SAF 2. Don's proposal that "Migration to Struts Action 2.0 should take hours, not days, weeks, but probably not minutes." is the part that refers to this, I assume. Gabe ----- Original Message ---- From: Ted Husted <[EMAIL PROTECTED]> To: Struts Developers List <dev@struts.apache.org> Sent: Friday, May 5, 2006 5:05:29 PM Subject: Re: What's the goal of SAF 2.0? (was Public API first draft ) On 5/5/06, Jason Carreira <[EMAIL PROTECTED]> wrote: > What's the goal of SAF 2.0? < > 1) Clean up some of the more annoying points of WebWork and XWork but > generally > have a backward compatible framework that WebWork users can easily jump on to > quickly +1 SAF 2.0 == WW 2.3 I'm still working off the original proposal that specified two phases. * http://wiki.apache.org/struts/StrutsTi The first phase is to bring over WebWork 2.x as is, resolve any licensing issues, package it as an Apache product, include a migration layer for SAF 1 developers, and move toward an initial release. The migration layer may yet include some tools, but, in my mind, the migration layer that matters is the grey matter. (Which is why I've been pouring over the documentation.) > 2) Take time to get things right, even if it means backward compatibility and > familiarity to > WebWork users takes a hit and it takes the WebWork community longer to > migrate. In my mind, this is still Phase 2. This might be SAF 2.1 or SAF 3.0, but it should come after we have done the preliminary work of Phase 1. -Ted. --------------------------------------------------------------------- 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]
