At 10:34 AM -0700 4/24/06, Bob Lee wrote:
I'm not sure two major releases is what's best for users.
- If SAF2 is going to be the same as WW2, why have it at all? I think
it will confuse users unnecessarily.
- We'll be stuck supporting WW2, SAF2, and SAF3 instead of just WW2 and SAF2.
- Some users will migrate to SAF2 and then will have to migrate again to SAF3.
- People will think we're incompetent and disorganized and that we
care more about playing than supporting users based on the fact that
we completely redesigned our framework twice in such a short period of
time (SAF1 -> SAF2 -> SAF3).
I think we're overestimating the amount of effort it will take to do
this right. Designing a clean API that we can support for the next 5
years should be our #1 priority. We can do a minimal amount of work on
the implementation so we can release ASAP and clean it up later.
I'm inclined to agree with Bob here. At this point, I think that the
first release of SAF2 should be taking the stage as more than just
WebWork 2.x with renamed packages. It doesn't need to be radically
different, but it should be more than that.
Joe
--
Joe Germuska
[EMAIL PROTECTED] * http://blog.germuska.com
"You really can't burn anything out by trying something new, and
even if you can burn it out, it can be fixed. Try something new."
-- Robert Moog
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
