Re: Zend API changes

Isn't that how it already works? bug list doesn't seem too much of a burden for me:) I just fix a bug at a time at my own leisurly pace. Although it would be nice to know what's more critical to fix and what's not. Otherwise I pick my own random bugs... Vlad Billy Rose wrote:

It is obvious that this project has a tremendous amount of effort from many people. Would it make sense to have someone, or a small group of people, whose task is to handle all of the release / testing issues? They would be "handed" over a release candidate from the development group to test and collect reports on. They then verify and classify all bugs and send reports back to the development team on a pre-determined time schedule, i.e. every 4 hours or such. As the test person / group collects reports, the development team works on new features / already known issues. Once new issues are reported, they are fixed and marked off the report list. After the release candidate is declared stable, it is put out there. This keeps the burden of trying to maintain a bug list, and deal with release issues off of the main pipeline of the development team. What do you think? ----- Original Message ----- From: "Zeev Suraski" <zeev@zend.com> To: "Billy Rose" <billyrose@billyrose.org> Cc: <php-dev@lists.php.net> Sent: Friday, May 04, 2001 6:33 PM Subject: Re: [PHP-DEV] Zend API changes

You can always suggest... :) At 02:14 5/5/2001, Billy Rose wrote:

The company I work for has a very quick bug turn over rate. I was

wondering

if I may make a few suggestions concerning release issues / bugtracking? ----- Original Message ----- From: "Zeev Suraski" <zeev@zend.com> To: "Hartmut Holzgraefe" <hartmut@six.de> Cc: <php-dev@lists.php.net> Sent: Friday, May 04, 2001 1:27 PM Subject: Re: [PHP-DEV] Zend API changes

At 21:05 4/5/2001, Hartmut Holzgraefe wrote:

PS: about the "welcome" thing above ... - you should know that i have put a lot of work into the manual (both english and german) and the function tables

Hartmut, I wasn't trying to understate your work on the manual; I told you personally that the function reference mechanism that you build was

very

impressive and useful. I wasn't being sarcastic when I invited you

(and

anyone else) to help document the Zend API. I know I won't be getting around to doing it in the near future, so if nobody else does it,

it'll

simply remain undone.

- afair there was someone who started to write a 'extension building manual' or something about a year ago and it was you , Zeev, who told him that this was useless effort as this was already beeing taken care off (without pointing him to this project or inviting him to join it) correct me if i'm wrong as i do not have found this posting in my archives yet

You're not wrong; It's been done and published (http://www.zend.com/apidoc/), and is the base for additional work

that I

invited people to improve on. Zeev -- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/ -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail:

php-list-admin@lists.php.net

-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net

-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/ -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net