Re: [Fwd: Re: [PEAR-DEV] Importing packages into CVS]
| From: | David Coallier | Date: | Fri, 30 Mar 2007 13:47:22 +0000 |
| Subject: | Re: [Fwd: Re: [PEAR-DEV] Importing packages into CVS] | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-46110@lists.php.net to get a copy of this message | ||
On 3/30/07, Stefano F. Rausch <stefano@rausch-e.net> wrote:
Sorry, hit the wrong button ... :) Cheers, Stefano ---------- Forwarded message ---------- From: "Stefano F. Rausch" <stefano@rausch-e.net> To: Christian Weiske <cweiske@cweiske.de> Date: Fri, 30 Mar 2007 15:42:10 +0200 Subject: Re: [PEAR-DEV] Importing packages into CVS Christian Weiske schrieb: Alexey,Ok, then lets agree on that: If some (QA) pear guy has fixes for a package that is not in cvs, and the maintainer does not react within the normal qa response times (as defined in http://pear.php.net/pepr/pepr-proposal-show.php?id=60, section "Fixing bugs/making releases"), the package will be imported into CVS, fixed and marked as orphaned. Eventually a release will be done to get the fixes out to the people. Isn't that why we have standards ? :) +1Although I doubt that even Christian is some kind of superhero able to work on all packages at once. ;] Thus my suggestion on importing the packages to CVS only when some actual work is to be done on them still stands.
That sounds reasonable and I second it! Cheers, Stefano -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php-- David Coallier, Founder & Software Architect, Agora Production (http://agoraproduction.com) 51.42.06.70.18