I have queried a couple of times the status. It seems that we just don't know.
I suggest cutting a release, calling it beta 2 and let it go through
the hoops of the IPMC.
My biggest problem at the moment with a release is that it always is
the code of one week ago: that is the time it takes from building it
and moving it through the votes.
Note that for a release only IPMC member's votes count as binding for
the final vote.
Martijn
On 6/2/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
Dear developers,
I'm having a look at the shiny roadmap that Martijn wrote on April
20th, and notice that 1.3.0 was announced for June.
Before 1.3.0, we need probably another beta and probably at least
one RC. Is there something preventing the release of beta2 say
today or tomorrow? Having a look at JIRA I only see this blocker
bug:
WICKET-606 AbstractTextComponent#setConvertEmptyInputStringToNull(true) does
not work with IObjectClassAwareModels (affects TextField, etc.)
Or is it too difficult to release while still being in the
incubator and you prefer waiting for the end of June? Please tell
me what is needed to move forward and I'll be glad to help.
--
Jean-Baptiste Quenot, keeping saying "soon" every time he's asked about
this
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
