All,
There are some patches still open. If we go into RC mode, those patches won't make it into 1.2. Also there are several bugs still open. In my opinion those should be either fixed or postponed until 1.3/2.0.
As there has been quite some tinkering with the framework I don't want to do a RC now unless everyone from core votes +1 and *STOPS* committing new stuff.
I think we should *really* stop tinkering with the framework and finalize it. We're hugging May for a final release of
1.2 this way. No more features or nice to haves please! Only bug fixes and documentation improvements. I also think that the need for documentation is much greater than another Ajax component or a rename in the API. We're going to break the api in the next version, everybody knows that. Documentation is scarce and pretty much non-existent, except for javadoc. This will not help newcomers. Having some good examples in article form (not just the examples project!) will lighten the load on irc and wicket-user.
Martijn
--
Wicket 1.2 is coming! Write Ajax applications without touching _javascript_!
-- http://wicketframework.org
- [Wicket-develop] Wicket 1.2 RC status Martijn Dashorst
- Re: [Wicket-develop] Wicket 1.2 RC status Johan Compagner
- Re: [Wicket-develop] Wicket 1.2 RC status Eelco Hillenius
