On Fri, Jul 12, 2013 at 07:08:41PM -0600, Mike Tutkowski wrote: > So, I haven't been following this thread in detail, but was curious: If > it's too much work to fix this by the end of the month (code freeze), what > are we planning on doing (moving 4.2 back or allowing this feature to not > exist in 4.2)?
I'm personally not happy either way, but I'd much rather not break existing environments in a new release on purpose.
