[x] Apache Wicket 1.4 (Non-binding vote) Having declared 2.0 a dead-end, you shouldn't release anything with the same version number within six months at least - there's too much potential for confusion IMHO. Not to mention tutorials and code snippets that are floating around labelled "for Wicket 2.0". Yikes.
Charlie. On 4/19/07, Gwyn Evans <[EMAIL PROTECTED]> wrote:
Wednesday, April 18, 2007, 11:04:12 PM, Martijn wrote: > There is a vote already in place for switching the development > branches around. Now it is time to name the release after 1.3 (and not > 1.3.1 :). > Apache Wicket 1.3 will be followed by: > [+1] Apache Wicket 2.0 (i.e. becomes our old 2.0 minus the c'tor change) I think there /will/ be a certain amount of confusion, but I do think that the jump to Java 2/JDK1.5, justifies the major version increment. I do however wonder if the following would be better... [ ] Apache Wicket 2.1 (one step beyond) /Gwyn
