Deprecation schedule

Lutger Blijdestijn lutger.blijdestijn at gmail.com
Tue Dec 7 16:25:36 PST 2010


bearophile wrote:

> Andrei:
> 
>> T0: documentation marked as "scheduled for deprecation".
>> T1: Function is deprecated and documentation updated to mention "has
>> been deprecated"
>> T2: Function is eliminated
>> 
>> Question is, what are some good values for T1 - T0 and T2 - T1?
> 
> T0 = T1 = 0 seconds
> T2 = 2 months (2 releases)
> 
> One year from now, in a similar situation:
> T0 = 0 seconds, documentation marked as "scheduled for deprecation in next
> release". T1 = 1 release (1 month)
> T2 = 3-6 releases (3 - 6 months)
> 
> Bye,
> bearophile

That is very harsh for T2, it means that at this point anything you write 
might not compile anymore with the newest phobos in just 5 weeks time. Even 
3 months is short, especially for a more stable point in time. I'd rather 
have T1 earlier and last longer, that way you can still compile the code.



More information about the Digitalmars-d mailing list