RE: [PEAR-QA] BC check on release upload

From: Date: Wed, 17 Sep 2003 10:14:39 +0000
Subject: RE: [PEAR-QA] BC check on release upload
References: 1  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-196@lists.php.net to get a copy of this message
> From: Pierre-Alain Joye [mailto:paj@pearfr.org] > Sent: Wednesday, September 17, 2003 12:06 PM > 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? Well even then I would say there must be a way to override this mechanism, but at that point we can make it impossible for the maintainer alone to make this decision for example. I do agree that maintaining BC according to our standards is a critical requirement in order for our infrastructure to work correctly. So this is a big topic indeed! Regards, Lukas

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