On Jul 31, 2005, at 1:05 PM, Jonas Maurus wrote:
Reasoning:
By now, Tapestry 4.0 is completely incompatible with the 2
production Tapestry
3-applications I have out there. A silent upgrade, or phasing-in of
Tapestry 4's
new features is not possible. Changing this now will save a lot of
pain later
and allow all new application development based on Tapestry 4 (I'm
currently
developing based on the beta releases) to go forward towards 4.1
without added
refactoring cost, while Tapestry 3 applications need major
refactoring anyway.
I've gotta say, I was actually with Geoff on this one. But your
argument makes total sense. I'd much rather have this change going
from 3 to 4 than from 4 to 4.1.
So, my vote is: +1 (non-binding)
--
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
