[PEPr] Comment on RFC::VersionNaming

Greg Beaver (http://pear.php.net/user/cellog) has commented on the proposal for RFC::VersionNaming. Comment: potential BC definition: backwards compatibility is defined by documented API at pearweb (pear.php.net/manual). All documented methods contain a signature, and a return value. If a method's signature or return value changes from the documented values at pear.php.net, then BC has been broken. If a package is not documented, BC is not possible, and the package may not be above "alpha" stability by definition. Incidentally, package.xml 2.0 provides the ability to assign differing stability levels for API and for package code. This will solve the question of not-feature-complete-but-stable, as this would mean a package stability can be stable, but API alpha. Alternately, if a new package is matching an existing API, the API could be stable, and the package alpha. For installation purposes, the least stable state should be used for comparison. Proposal information: http://pear.php.net/pepr/pepr-proposal-show.php?id=65 -- Sent by PEPr, the automatic proposal system at http://pear.php.net