OK, I'm cutting a release *NOW*
Martijn On 4/19/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
On 4/19/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > All, > > Since we did the package rename, and now that biggest API breakers of > the backports are in, shall we now build a new release for 1.3? This > release would be made available to the larger community. The IPMC > would be much more willing to check it in this case. > > Questions: > - should we create a release this weekend? you mean a public release? that depens on whether or not johan can get the attach/beginrender refactor in before then. that will break clients, so we should get it in before doing any soft of public release. - how do we label it? [alpha, beta, general availability, ...] if johan gets the refactor in call it a beta because they all major tweaks are in. if not, and you still want to make a release, call it alpha. and whatever you do, no matter how desperate you are, do not call it general availability. -igor Martijn > > -- > Learn Wicket at ApacheCon Europe: http://apachecon.com > Join the wicket community at irc.freenode.net: ##wicket > Wicket 1.2.5 will keep your server alive. Download Wicket now! > http://wicketframework.org >
-- 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
