Christian Stocker wrote:
Actually, other people i talk to are always impressed, how this
"chaotic", based-on-common-agreement developement process actually works
at all ;)
Well, one reason might be no matter how fuzzy the process
there are some very clear metrics for the result, like
e.g. "compiles", "passes tests" or, a little more fuzzy
but still rather fact-based, "works". And you can apply
all these to different scales of changes. Combine this
with the fact that the effort needed to implement changes
does not include any noticable cost of creating a copy
first and you'll find that creating software is very
different to other forms of science, engineering and
art.
This doesn't stop us from having some PEP-like documents, which clearly
define some common rules, but I fear we end up in heavy discussions on
wording and details. See the PEAR mailinglists for an example ;)
oh yes, the only list that i'm subscribed to but have
activated the "mark message as read" option in the
filter ;)
--
Hartmut Holzgraefe <[EMAIL PROTECTED]>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
