[Asterisk-Dev] removing depreciated code?

[José Pablo Ezequiel Fernández]

On Saturday 24 September 2005 12:59, Roy Sigurd Karlsbakk wrote:
> >> Are you sure this is a good thing? Having the backward
> >> compatibility  is one thing, but then if something doesn't work,
> >> the general answer  from
> >
> > perhaps a solution could be found by #ifdefing the deprecated code
> > around say, DEPRECATED_1.2, and then making it a compile time
> > option in the makefile to either build with backward compatibility
> > or to have it removed for those who'd prefer it without the
> > deprecated code.
> >
> > i'm making the big assumption here however that it's as simple as
> > wrapping ifdefs around the code which needs to be taken out.
>
> that sounds to me a brilliant idea. that way it will be possible to
> try out and test a clean 1.2 installation..
For me it sounds very messy, it'll be very easy to wrap some parts and not 
some others leaving something that works part of the time.
Personally, I believe no code should be touched once a project enters in beta 
state except fo fixing bugs, and the same goes for increasing minor numbers, 
so 1.2.1 is a better 1.2.0 (in the sense of stability, not feature-wise).
I'd say remove the depricated code after 1.2.0 is released and not for the 1.2 
branch but for HEAD, for what will become 1.3, or 1.4 or 2.0 or whatever.
-- 
José Pablo Ezequiel Fernández