Basically what I'm saying is that Wicket 2.0 is a fine version as far as I know, and if there are nasty bugs in it, start shouting here and they'll be fixed asap. It will just take a while before we get to a final release, and we might break the API on a few occasions still (though that should typically be nothing really big).
Eelco On 1/30/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
It really depends on your developer team on how comfortable you are working on beta versions. If you can find your way around Wicket a bit, and you do find important bugs, we are typically fast to respond, whichever version it is. And if you have no problem building snapshots yourself, you can work on 2.0 today. Wicket 2.0 and 1.3 only differ in a few areas, but the code base is still much the same. So... I would say if you have a project that has to be done this summer or later, go for Wicket 2.0 - that is if you are ok with building your own snapshots or even working from svn directly. For more urgent deadlines, 1.3 is probably better. Also because most of the core developers are working on projects with that version, so any updates to 1.3 are immediately tested in real-life applications. Eelco On 1/30/07, Jon Steelman <[EMAIL PROTECTED]> wrote: > Then for using 2.0 how far out a deadline would you folks recommend > for a project someone is beginning now? > > Jon > > On 1/30/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > He talked about a March 30 deadline, so I think 1.3 would be the best > > between the new features we support and stability. > > > > Eelco >
