One thing you could do to help out, is to make sure we have all the missing part of the old 2.0 branch on our plate and in JIRA, assigned to release 1.4M1. This would make our job a lot easier and will prevent disappointments when we miss a particular feature.
Another option is to add them to the 1.4 wishlist in our wiki. And this is open to everybody in the community. You don't have to be a core developer to discuss the future of the framework (though we reserve the right to go into another direction). Join us on the development list and help out by discussing, proposing new or missing features, etc. Martijn On 1/14/08, Stefan Lindner <[EMAIL PROTECTED]> wrote: > > We haven't started it. > > > > We wait with starting new development until 1.3.1 or even 1.3.2 is > > released. We don't want to maintain two branches and first want to > > make the issue list for 1.3 a lot smaller before branching. > > > > Martijn > > This means, that we old wicket 2.0 users who are waiting for Generics, > have to wait still some other months until 1.3.2 is done? No parallel > development of 1.4/2.0.0? It's hard to be a wicket 2.0 user. Can you > give us any timeline for 1.3.2/1.4/2.0? > > Stefan > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
