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
On 1/14/08, Stefan Lindner [EMAIL PROTECTED] wrote:
Where can I find
If you want to know when branches like this happen, subscribe to the
dev list. We always vote for these kind of decisions, and for releases
etc.
Martijn
On 1/14/08, Martijn Dashorst [EMAIL PROTECTED] wrote:
We haven't started it.
We wait with starting new development until 1.3.1 or even 1.3.2
Where can I find the subversion branch for wicket's next release? At
http://svn.apache.org/repos/asf/wicket/trunk/jdk-1.5/ I can't find the
wicket base package.
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
On 1/14/08, Stefan Lindner [EMAIL PROTECTED] wrote:
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
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
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
Dear Martijn,
I understand your point of view and I did not want to blame wicket. We
use wicket because we love wicket. Unfortunately we started using Wicket
2.0 early in 2007. The main reason for doing this was the ability to use
the generic components of wicket 2.0 (version 2007). Once we have
