Remy Maucherat wrote:
Mladen Turk wrote:
My little tweak will most likely be ported back to 5.5.x. As a result,
when you install a new build, you'll get a warning, and the code will
not use the problematic method by default. As a result, the forced
upgrade is a waste of time for most.
OK.
So I am against this plan. I've stated my position already: unless
there's an API change that was needed, the minimum version number should
not be upgraded.
Also fine. The problem we have is the 1.1.5 that eats the CPU.
The 1.1.3 as minimum means that any version up to recommended is
allowable, which is not the real case.
Anyhow, this should at least be clearly documented if not enforced.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
