> I'd recommend that we keep the constant for now so that everybody's
> code compiles, document it as useless and deprecated, stop using it in
> our code so we don't set a bad example, and remove it with the next
> big API change (2.1?).

+1

Time to start the laundry list of things we need to do as soon as
we hit/branch 2.1.

-aaron

Reply via email to