Re: PEAR Quality (vs. Quantity) RFC
| From: | George Schlossnagle | Date: | Tue, 13 May 2003 19:04:10 +0000 |
| Subject: | Re: PEAR Quality (vs. Quantity) RFC | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-16220@lists.php.net to get a copy of this message | ||
On Tuesday, May 13, 2003, at 02:57 PM, Martin Jansen wrote:
On Tue May 13, 2003 at 12:1256PM +0200, Wolfram Kriesing wrote:I agree. This is much easier to automate as well, as part of the package verification step on submission.* Stage 2 (minimal req.) - CS compliance The package should be checked for compliing to the PEAR-CS rules. If that is not the case the package should not even get accepted in PEAR.IMO it's better to not allow releasing a package that does not apply to the coding standards. Putting code, that isn't CS compatible, into CVS should be allowed.