Please complete the user guide (eg form validation) before 4 final is
out. this looks bad for a serious framework.
cheers,
Ron
Brian K. Wallace wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Howard Lewis Ship wrote:
By the time this vote ends, we'll have some kind of fix for
TAPESTRY-724. I think, with that, Tapestry 4.0 is ready for prime
time. We've already had the discussion of outstanding bugs needing
fixing. I think we should get 4.0 out the door.
Howard M. Lewis Ship: +1 (binding)
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
While I'm more than anxious to see 4.0 released...
Considering what's riding on this issue (Spindle being a major
contributor to easing Tapestry development), I'd rather hold off any
vote until the "some kind of fix" works for tooling. Not saying it
wouldn't, but I don't see how holding off the vote until then would hurt.
- -0 (non-binding) until then
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFDjm+saCoPKRow/gARAsSYAKCCj50ePxiKfcEH1lY/39acwCvw7gCfZ3Qz
8Cv3ufif91dCQI0dQJ7ijU4=
=dGLD
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]