Mark Stang <mstang <at> pingidentity.com> writes: > > Howard, > Great, how close is Tap 4 to being Production Ready? > Is it stable enough for us to switch? We are going GA on > Novemeber 11. And we have a month of QA before that. > So, the question is, will Tap 4 be stable enough by then? > > thanks, > > Mark
Given that there is now a discussion to remove the action service, there has to be a beta-5. After the beta phase there's usually at least one release candidate. Taking the timeframe between beta-3 and beta-4, you won't make it into QA with Tapestry 4.0 final. If by "switch" you mean "from Tapestry 3", there's almost no way you can do that in this timeframe unless it's a small application. Stay with Tapestry 3 until GA and then plot a careful timeframe for a migration when Tapestry 4 has a release candidate and is therefor feature stable. Tapestry 3 is still a great framework to use. No offense, but the rate at which Howard changes Tapestry's implementation means that "beta" in Tapestry jargon does not mean "feature complete" as it does in my company :-). Tapestry 4 is generally incompatible with Tapestry 3. Once you've ported multiple applications it's probably not that hard to do, as most of the problems that occur are the same over and over again, but doing it for the first time, you'll have a lot to learn and refactor (Hivemind, Annotations, attribute prefixes, IEngineServices need to be contributed... and so on) cheers, Jonas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
