Re: BC check on release upload

From: Date: Wed, 17 Sep 2003 10:06:18 +0000
Subject: Re: BC check on release upload
References: 1 2  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-195@lists.php.net to get a copy of this message
On Wed, 17 Sep 2003 11:56:54 +0200 "Lukas Smith" <smith@backendmedia.com> wrote: > Anyways making this such a hard rule removes common sense. > If we don't trust the developer to know what he is doing when he > presses"yes I am aware of these changes and they don't result in a BC > break to any public class/method/function" then we might as well > forget about PEAR development model itself. I agree here. Until we take care of phpdocs, only warning should occur. The phpdoc tags check will verify that a public function/class/method has not changed to private. But do we agree to make it to make it an hard rule once phpdoc are also analyzed? pierre

« previous php.pear.qa (#195) next »