Re: getting a QA'ed package release
| From: | Paul M Jones | Date: | Thu, 04 Mar 2004 20:37:43 +0000 |
| Subject: | Re: getting a QA'ed package release | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-26100@lists.php.net to get a copy of this message | ||
Hi,
I would prefer an approach like that. It would help us avoid situations where QA is bogged down in other matters, preventing a timely release because QA is overloaded. -- Paul M. Jones Savant: the simple alternative to Smarty. http://phpsavant.com/What about adding this to the release workflow, so that the new package doesn't get released until checked by QA?Halting the release until approved by QA seems like adding unneeded friction to the process. How about having the releases reviewed by QA and stamped on approval? This would allow for "quality seal" requirements to vary and include future stuff, like PHP5 compatibility, coding conventions or proper tutorial documentation. It's about the same concept, but asynchronous.