RC1

Juergen

On 4/11/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> Forget about those changes. I don't care about them that much. It just
> seemed to be important for some users.
>
> Eelco
>
>
> On 4/11/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> > RC1, thursday is fine.
> >
> > Or if eelco/others really want to RequestCycle changes? Then another beta
> > and then it could be now i guess.
> >
> > johan
> >
> >
> >
> > On 4/11/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> > >
> > > There was an agreement to release beta4 or rc1 today, however given the
> > number of changes, I suggest a cool-down until thursday evening?
> > >
> > > Next release:
> > > [ ] beta4
> > > [ ] rc1
> > >
> > > When
> > > [ ] now!
> > > [ ] thursday evening sounds great, thank you
> > > [ ] what? This soon? you got to be kidding! Come back next week!
> > >
> > > Martijn
> > >
> > >
> > > --
> > > Wicket 1.2 is coming! Write Ajax applications without touching JavaScript!
> > > -- http://wicketframework.org
> >
> >
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
> _______________________________________________
> Wicket-develop mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to