Stefano Bagnara wrote:
> > I've not formed an opinion on whether or not to fix this for v2.3 or
wait
> > for v2.4. I won't form an opinion until I see the proposed patch.
> Instead, as time passes, my idea for delaying it to 2.4 is stronger.
Having seen the proposed patch, I'd agree that it belongs in v2.4. As do
Norman and Vincenzo. For v2.3, Vincenzo proposes removing the docs for
these filters, presumably so that no one knows that they are present. Or
perhaps we should simply include a warning in the docs.
> If we release 2.3.0 final soon we can start working on 2.4 and add this
> and much more new features!
Remember: 2.4 === LOW-RISK, HIGH-VALUE.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
