On 3/30/07, dukejansen <[EMAIL PROTECTED]> wrote: > > I too am working on a system which must go live to a large user base early to > mid July. > > What kind of confidence can I have that 1.3 be stable enough by then? Are we > talking 95%, 75%, or 50%?
95% or more. > I need some of the 1.3 functionality but once I commit to move to 1.3 I'm > not going to have time to go back to 1.2 if bugs start popping up all over > the place. > > Any good place to see what kinds of stability problems are present - i.e. if > they are in parts of the framework not being used, etc? I have a pretty good feeling about 1.3's stability. The only thing that may an issue the next 1 or 2 months is that we're still backporting 2.0 features. You can track what needs to be done still here http://cwiki.apache.org/confluence/display/WICKET/Backporting+features+from+trunk and of course, with every back port there is the possibility we break/ forget something. But like I said, at least a number of people of the Wicket team uses 1.3 for their day jobs, so if anything went sour we'll know and fix quickly! Eelco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
