All, After the luke warm responses on outstanding bugs for Wicket 1.2, I want to move to release 1.2.3.
This release contains: - wicket - wicket-extensions - wicket-examples - wicket-quickstart - wicket-spring - wicket-spring-examples - wicket-spring-annot - wicket-spring-annot-examples - wicket-auth-roles - wicket-auth-roles-examples The release will be released outside of Apache on the sourceforge.net servers. The releases will contain a notice file stating that this is *not* an Apache endorsed release, as will the website and the release notes. The fact that we are building a non-Apache endorsed release means that the release will not include 'incubating' in the name and version, and that we don't have to check the license headers and can include the LGPL licensed DatePicker in extensions. These things will have to change for releases built and released inside the ASF. Included in this vote is the proposal that we wait one week for marking the 1.2 release final and go into maintenance mode only for 1.2. This means that this time we *WILL* create a wicket-1.2.x branch for 1.2 when the week has passed without serious bugs. I know that it will be a pain to maintain and fix bugs in 3 branches, but it is something we have to do someday soon. Wicket 1.3 can then progress in branch 1.x and we can make our first steps towards graduation. May I have your votes please? This vote will close sunday morning, CET. [-1] Don't release 1.2.3 [ 0] I don't care [+1] Please, I've waited toooooo long for this already Martijn -- <a href="http://www.thebeststuffintheworld.com/vote_for/wicket";>Vote</a> for <a href="http://www.thebeststuffintheworld.com/stuff/wicket";>Wicket</a> at the <a href="http://www.thebeststuffintheworld.com/";>Best Stuff in the World!</a>
