Re: Re: deprecating

From: Date: Tue, 19 Jul 2005 17:25:23 +0000
Subject: Re: Re: deprecating
References: 1 2 3  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-38729@lists.php.net to get a copy of this message
Supposedly you can, but according to the RFC any change in the API would require I roll out some other package (ie. Foo_Bar2). The problem with this package is that 0.2 was released stable (evidently before this RFC was accepted) and then magically jumped to 1.0.1beta. Also, since when is deprecating something breaking backwards compatibility? It would still function as it did before. And, if I deprecate something going from 1.0 to 2.0 (but leave it there, while changing all docs) why can't I remove it in 3.0? People would have had an entire major point release to prepare for the change. Also, if my API doesn't change do I still have to move everything into a new package? Multiple new packages makes pretty much zero sense - after all this is exactly what version numbering is for. You should know that 1.0 and 2.0 have different feature sets without having to install 14 different versions of the same package. A better approach, IMO, would be to have package.xml enable developers to somehow warn a person about potential problems *before* pear installed the new package. For instance, pear would notice that I'm going from 1.0 to 2.0 and stop to tell the person upgrading that upgrading will cause X, Y and Z to break and to update their code, if needed, before installing. --Joe On Jul 19, 2005, at 10:15 AM, Joshua Eichorn wrote:
Lukas Smith wrote:
Joe Stump wrote:
OK, On another note, what if I have an old package (I do) that has a function named foo_bar(). This package has only one stable release (0.2) and one beta release (1.0.1beta). Can I deprecate foo_bar(), have it call fooBar() and then throw a notice that it's deprecated when it's used? If so, then how long do I have to wait to finally remove the deprecated function? One release? Two?
IMHO you cant deprecate a method inside a major version, since that is effectively a BC break. regards, Lukas
You can still change the api in anything that hasn't has a stable release right? -josh --PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php


« previous php.pear.dev (#38729) next »