Hi Matthew!
I'm curious how that's a good tradeoff. You're suggesting that (for example), dynamic properties be deprecated in 8.2, but not actually throw a deprecation (with or without the supressing attribute) until, say, 8.4, and then in 9.0 they'd error hard without the attribute?
The logistics for Internals aside for the moment, wouldn't that mean for most users they'd suddenly get hit with a massive wall of deprecations all at once? Or is that the idea, that the major library producers just take one year off every few years to deal with deprecations but can ignore them between now and then?
I suppose I can see the point, but we normally tell people to not wait longer to address issues. Would the total time invested be that different? (I really don't know; I'm not even close to being in your shoes.)
Without the deprecation notices, though, people who wanted to get a jump on the process earlier (those of us who have only single-digit libraries to keep track of), wouldn't that make it harder, because the engine isn't pointing out where we need to make updates for us?