> Well, I think you should start with 4 even if it's named beta right
> now, plus that you could switch to release when it will be available
> (not so far), looking at 4.0 as the unstable and untrusted branch is a
> wrong assumption right now. We even may see RC pretty soon.
> Read the archive and look at source changes to trust yourself.
> I've not considered stupid "political" reasons.
It's nothing particular about Tapestry, but I've been burned before
by targeting Beta releases. The problem with betas is the target tends to
move so I'm forever going back and changing things that were
deprecated/changed between, say, Beta 1 and Beta 8. Likewise Betas, by
definition, are untested and hence more likely to have bugs.
With Tapestry 3.0.3, it doesn't have all the bells and whistles of
4.0, but A) it works B) it's stable, C) I'm *confident* in it, so if
something doesn't work, I can focus debugging on my code, whereas in a Beta
I have to debug the Beta as well, doubling my search space.
I'm not quite as bad as some of my clients who have an unofficial
rule of "no x.0 releases", but I do, as a rule, stay off betas and anything
with a 1 in the major version number :) (although, I must confess, I got so
annoyed at Jasper I swithed to Eclipse's BIRT which is, at best, beta
Quality atm and it's reinforcing my prejudice against early releases).
--- Pat
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
