Deprecation schedule

[Daniel Gibson]

Andrei Alexandrescu schrieb:
> I wonder what would be a good deprecation schedule. Consider 
> http://d.puremagic.com/issues/show_bug.cgi?id=5257 as an example.
> 
> We should now slowly deprecate std.utf.count. How should we go about it?
> 
> 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?
> 
> 
> Andrei

T0: As soon as it's decided that the function will be replaced

T1: Once the replacement is available and usable (tested, considered mostly stable)

T2: If the function was available in phobos1: never/for D3. That would make 
porting of D1/Phobos1 code to D2 a lot easier - one could replace the use of 
deprecated functions bit by bit instead of having to overhaul the whole project 
before being able to compile it for D2 - or, at least you'd only have to fix 
stuff concerning changes in the language (const, TLS, etcpp) at first.
If it wasn't available in phobos1: Within 2 or 3 DMD releases?

Cheers,
- Daniel