[PEPr] +1 for RFC::VersionNaming
| From: | Greg Beaver | Date: | Mon, 22 Nov 2004 02:28:15 +0000 |
| Subject: | [PEPr] +1 for RFC::VersionNaming | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-34473@lists.php.net to get a copy of this message | ||
Greg Beaver (http://pear.php.net/user/cellog) has voted +1 on the proposal for RFC::VersionNaming.
Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=65
Vote information:
http://pear.php.net/pepr/pepr-vote-show.php?id=65&handle=cellog
Comment:
I likee.
BC can be defined simply by consensus, but should hinge on API
documentation's definition of parameters and return values. There has to
be a gray area, but if we define it in terms of documentation, arguments
can be resolved easily (either the code is wrong, or the docs are wrong)
--
Sent by PEPr, the automatic proposal system at http://pear.php.net