I didn't push the released button because I hadn't actually built it :)
I had forgotten that the release can also be 'unreleased', like I did for the previous version. I'll remove the tags and do those steps again, this one seems really like one I want to have anyway :) I'll document the steps taken too [1] Martijn [1] http://issues.apache.org/jira/browse/WICKET-662 On 6/18/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Igor Vaynberg (JIRA): > > [ https://issues.apache.org/jira/browse/WICKET-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > > Igor Vaynberg resolved WICKET-614. > ---------------------------------- > > Resolution: Fixed > Fix Version/s: 1.3.0-beta2 This is pure nitpicking, but I think the fix version should be beta3, as Martijn seems to have copied trunk to beta2 a few hours before. I guess we also need to revise the release process, adding an extra step requiring to mark JIRA version as released. beta2 still shows under "unreleased" versions. WDYT? -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/
-- Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org
