On 11/6/2018 5:24 PM, Rochelle Grober wrote:
Maybe the fastest way to get info would be to turn it off and see where the
code barfs in a long run (to catch as many projects as possible)?
There is zero integration testing for lazy translation, so "turning it
off and seeing what breaks"
I seem to recall list discussion on this quite a ways back. I think most of it
happened on the Docs ml, though. Maybe Juno/Kilo timeframe? If possible, it
would be good to search over the code bases for places it was called to see its
current footprint. I'm pretty sure it was the docs folks
On 11/5/18 3:13 PM, Matt Riedemann wrote:
On 11/5/2018 1:36 PM, Doug Hellmann wrote:
I think the lazy stuff was all about the API responses. The log
translations worked a completely different way.
Yeah maybe. And if so, I came across this in one of the blueprints:
