Hi,
I have been watching tapestry release semantics for many years now, as they
happen, as they impact the commercial field and related hurdles.
Given the maturity of the framework and it's concepts... is it reasonable to
ask for the following:
o Tapestry 5 be 100% commercially validated and qualified
o Tapestry 5 provide tooling to migrate ALL
tapestry-4.* framework based application sources
(yes my tap 4 applications) to be tapestry 5 compliant
automatically
Any tapestry 4 webapp migration semantic is finite and concrete. It just needs
to be automated... (components, pages, services, etc...)
Not trying to start a firestorm and thanks to the layman who have put their
heart into it so far... The framework is fun and likeable and I use it for
obvious real and good reason. June 2007 target was missed for tap5. Would like
to try and refrain from getting caught into the same release cycle semantics
that have occurred in the past. Are sincere efforts being considered to prevent
repitition? If so are the above requests reasonable?
Feedback on feasibility and possibility is appreciated.
Personally I would like to see this happen.
Best regards Ken in nashua
_________________________________________________________________
Watch “Cause Effect,” a show about real people making a real difference.
http://im.live.com/Messenger/IM/MTV/?source=text_watchcause
