Re: Re: bug #48247 again

On 16.06.2009, at 18:56, Stanislav Malyshev wrote:

Hi!

So lets delay fixing this issue until 5.3.1? Of course it can be fixed in HEAD right now :)

Delaying the fix would mean we release 5.3.0 that in mostly default config has an infinite loop bug. Maybe we can at least have temp fix and then when we have a proper one then remove it (or leave it in, it wouldn't hurt anybody)? For 5.2 it's even worse since I understand 5.2 is not intended to be developed past 5.2.10, except for security fixes.

so if this issue is also in 5.2 .. i feel even less inclined to delay a stable 5.3 release because of this issue. have we made it worse in our attempts to fix it? the fact that this bug isnt fixed yet could mean several things like: 1) the issue affects few users 2) the issue is so complex that we continuously try to fix it and fail both issues do not sound like good reason to delay 5.3 from where i stand. regards, Lukas Kahwe Smith mls@pooteeweet.org