I think it would reckless of me to recommend anything that may or may not affect anyone's job/career..
That being said - if it were me - yeah I'd totally go for it. It's probably been a mistake to wait so long for 4.1.1 to come out anyways. Probably I'll just fix this validation message issue and release it. On 12/5/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Okay, I know Jesse is probably fed up with these types of questions! And we've gone over it before, about 4.1, 5.0, roadmaps, etc, a couple weeks ago. The 4.1 "snapshot" that's out right now, for a relatively simple app - no custom components, hivemind services, Java 1.4 so no annotations, and maybe a sprinkle of DOJO stuff (hence the reason to switch to 4.1!!) - would moving from 4.0 to 4.1 be a horrible idea? I skimmed over a lot of the open issues on JIRA and none seem too severe, or too widespread to some of the "proven" core of tapestry. Our application is for our internal staff (a dozen or so), and since it's relatively small, is usually decently tested for bugs. So it's not like I'm re-writing Amazon.com or something with Tap4.1 and will lose billions of dollars over a bug.. 4.1 looks really nice, and it would be great to jump in, rather then do it in 4.0 and then re-do it in 4.1 in 6 months. That said, go for it? All comments apprieciated! Thanks, Greg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
