that all depends on how long the development is planned for!
If they like to have java 5 and can live for a few months with a bit moving target. then 2.0 could be a good choice. especially on the long run, if you do now 1.3 you will never go to 2.0anymore johan On 1/30/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Yeah, 1.3 is the best to go if you're ramping up for development now. Eelco On 1/29/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > i would go with 1.3 branch. 2.0 is still unstable and if you have a deadline > i wouldnt go with it > > -igor > > > On 1/29/07, Alexei Sokolov <[EMAIL PROTECTED]> wrote: > > > > Hello wicket developers, > > > > I need your advise as to what version of wicket to use for our new > > website. > > > > Currently, we have some code using 1.2.3, but we are planning to start > > coding much more aggressively very soon. We are trying to hit March 30 > > deadline for our beta version, and so far it looks like 1.2.x is our best > > choice, but with api changes coming in 2.0 it seems like it will be > > difficult to switch to that version later. So please help me make the > > right > > choice: > > - use 1.2.x and live without newer extensions/libraries (scriptaculous > > integration lib requires 2.0) and potentially live with 1.2.x forever > > - use 2.0 and run early 2.0 beta code on April 1st, with a possible > > upgrade > > to 2.0 final somewhere around summer'06 (please let me know if this is not > > realistic to have it by summer) > > > > Thank you, > > Alex > > > > >
