> On Jul 8, 2021, at 1:26 PM, Rowan Tommins <rowan.coll...@gmail.com> wrote: > > for the record, here is what I think: > > * Removal of a deprecated feature can be at any point in the future, even the > indefinite future, just not "never". > * Very short deprecation periods can be harmful, because they don't give > people enough time to change. > * Very long deprecation periods can also be harmful, because people will put > off making changes, and end up with a large back log when things are finally > removed. > * Specific plans are useful to users - "this will be removed in 2024" is easy > to base decisions on. > * Failing that, any plan is better than no plan at all - it's easier to work > with "a decision on this will be made in 2023 based on an estimate of usage > at that point" than "at some point between 1 and 100 years from now, we'll > remove it without further notice".
That is a policy I can concur with. _Definitely_ better than what was stated earlier in the thread. Does anyone else disagree? If no, could this get memorialized on the wiki somewhere to reference in future discussions, if needed? (Or does it need an RFC?) -Mike -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
