Time scale for Wicket 2.0 is to start out releasing betas within two months. We plan to finish Wicket In Action the next few months - say october - and we really want the 2.0 API stabilized by then, as we're covering 2.0. The major changes we had in mind for 2.0 have been in for a few months now, and as we have converted all the core components/ projects, and most of the wicket-stuff projects, we have good proof everything works (really) well. We are currently discussing the last API tweaks, most notably Wicket's models, but once that is done and proven, we are ready for beta.
Eelco
As for 2.0, we may well want to release wicket-incubating-2.0-RCx or similar, but I'd have hoped that we'd be out and able to do apache-wicket-2.0 by the time we finalise 2.0. (Anyone any idea what sort of timescales we might be expecting, by the way). /Gwyn On 27/07/06, Johan Compagner <[EMAIL PROTECTED]> wrote: > > imho, i would much rather see wicket-1.2.2 rather then > > wicket-incubating-1.2.2 as a release. to me incubating says "not ready for > > production use". it might mean something different in the apache context > > but > > we cant expect all our existing users or those who stumble upon wicket for > > the first time to enlighten themselves. > > > > so i would rather release on our existing home at sf.net > > > Yes i would also rather see a normal wicket-1.2.2.jar when we release an > update > to 1.2.x then a incubator name in it. 1.2.2 is a finished release and > incubator > doesn't say finished to me and that i guess goes for a lot of people. > > So i am +1 for option 2. > > And for 2.0 we should then really wait for getting out of incubator. Because > the same rules apply to me. I am not pro for a final release with incubator > in the name. > > johan > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
