Yes. Someone on IRC reported seeing a leak as well. Bug can't hardly
get more serious than that. Could you expand a little bit as to when
that happens?

Btw, another thing we should do for 1.2.6 is set max versions to a
more humble valued by default.

Eelco

On 2/11/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
Yesterday i just fixed the AccessStackPageMap in 1.3 (that is the one used
in 1.2)
there is a bug in it that it leaks pages into the session under specific
circumstances

so maybe a 1.2.6?

johan


On 2/10/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
>
> Sure. So we have this release, which is great and let's leave it with
> that. We can make a new 1.2.x release in a few months if there is
> demand for it and if there are more bugs that have to go into it.
> Meanwhile if people run into issues they can find out they were
> reported and fixed and build themselves. Those two fixes are
> potentially nasty, but as it doesn't seem to touch most of our user
> base, I think we can focus on getting on with 1.3 and 2.0.
>
> Eelco
>
>
> On 2/9/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> > On 2/10/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > > On 2/9/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> > > > What problems are you talking about?
> > >
> > > The ones Frank reported.
> >
> > Though for an Apache release very important and a showstopper, they
> > are not for a sf.net hosted release. I'd rather spend the time
> > building 1.3-beta1 than fixing these issues in 1.2.x
> >
> > Martijn
> > --
> > Vote for Wicket at the
> http://www.thebeststuffintheworld.com/vote_for/wicket
> > Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now!
> > http://wicketframework.org
> >
>

Reply via email to