Re: BC check on release upload
| From: | Greg Beaver | Date: | Wed, 17 Sep 2003 12:56:27 +0000 |
| Subject: | Re: BC check on release upload | ||
| References: | 1 2 3 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-197@lists.php.net to get a copy of this message | ||
David Grant wrote:
There is - it will require some fancy footwork, however, unless PEAR wants a dependency on PHP_Parser when it comes out with 1.0. I would highly recommend that this feature remain simply a warning that requires additional developer interaction for at least the next release of PEAR, and possibly 2 releases, to be sure that all issues are worked out with the packager. In other words, this should be done at the packaging stage as well - packaging would fail, unless a --iknowwhati'mdoing option is specified :). GregOn Wed, 17 Sep 2003, Pierre-Alain Joye wrote:But how would one be able to tell this? This is currently dependent on either someone using an underscore character (_) to prefix the class (or relevent documentation tagging). If this is not the case, then one might get erroneous results. Is there a way of requiring packages to be documented properly?A release is rejected if: - A Class has been droped - a function or method has been dropedI quess this should be if public function has been dropped?