Officially, we haven't even started. Despite the advantages of T5 in streamlining the core ideas of Tapestry and *possible* performance improvements, T4.1 offers (sometimes in its wonderfully quirky way, but nevertheless) most of what T5 does and more. I speak for myself but I'm sure a lot of the T4 developers share the feeling; while there's interest in moving to T5, we don't want to get held up by some not-yet-implemented feature that worked just fine in T4 (e.g. update components, call javascript after ajax, localized resources etc.), so we are still at the starting blocks with T5. I mention T5 so frequently as I think it's pretty clear to all of the Trails users & developers that the current and even next versions will be inherently Tapestry-based.
Kalle
