Current one sounds easier to me. Then we don't have to rush a new release with a new vote etc.
Eelco On 5/7/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Our release is a bit borked for maven users due to the fact that I didn't deploy the jdk-1.4 and jdk-1.5 parent poms to the repository (the release profile explicitly excludes them). This is something that needs to be fixed for future releases, and in my opinion for the current release too. We can either fix this one in the current release, or fix the build and vote for a release of beta 2. What do you guys think? For our mentors (which is why I cc'd @private) : given that we still are in the incubator, what would be a procedure to fix the current beta 1 release? Martijn -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org
