Re: not-yet-draft RFC on the new versioning standards for PEAR2 (needs PEAR Group sponsor to be official)

From: Date: Mon, 29 Jun 2009 04:48:49 +0000
Subject: Re: not-yet-draft RFC on the new versioning standards for PEAR2 (needs PEAR Group sponsor to be official)
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-52256@lists.php.net to get a copy of this message
Hi Greg, > API 1.0.2/stable, Release 1.0.3/stable <-- bugfix, API bugfix Just to be clear: An API bugfix means that e.g. I forgot to add a default value for a function parameter (like " = null"). Nothing else. No semantic changes. - Do method additions count as bug fixes? I can't think of any other API bugfix cases that do not break BC. - Renaming and removing methods are clearly not bugfixes, since they break BC. - Renaming, adding or removing private properties is completely out of scope because they are private. - Protected properties and methods fall under the same rules as public ones, because they are exposed to extending classes. -- Regards/Mit freundlichen Grüßen Christian Weiske -= Geeking around in the name of science since 1982 =-

Attachment: [application/pgp-signature] signature.asc
« previous php.pear.dev (#52256) next »