Re: PHP 4.0.0 Release packaged

-- Christian Wenz <[email protected]> wrote:

> As I understood the original posting, the tone was rather suggesting
> how the production cycle could be amended and some points of
> criticism web developers have towards PHP and what could be done
> about that. I also found that the original posting was well intended.
> If I had the
> impression that the original posting had the tone and content you
> described above, I agree with you. Maybe just my perception was
> different.

Consider the difference between the two "suggestions" below:

	Hi guys, I just had a great idea for how to improve the stability of
    PHP releases. Here's what we could do: <insert idea here>. I'd be
    happy to do the work to get it started, but I'll need some pointers
    on how to do <insert plan here>.

	Hi guys. Look, I know PHP is a really great system, and very stable
    and all, but I don't understand why you guys are so unprofessional
    about your releases. You need to do <insert idea here> before
    packaging a new release, or you won't be taken seriously in the real
    world. For example, bug #XXXX affects me directly, and even though
    I've complained about it for months, you haven't fixed it yet. As
    a result, I've been telling people who use my product not to upgrade
    to PHP4. Why can't you guys take constructive criticism?

YMMV, but I suspect that the first approach will be get a warmer 
reception. Look at the recent discussion about documentation in PEAR. 
Even though the core developers foresaw problems with the Ulf's idea, 
the discussion was amicable and productive.

On the other hand, I'm suprised at how often the second approach is 
used, and how polite the response usually is. I think that the PHP 
group is actually very professional. They write very good code and they 
manage a pretty large project from points scattered around the globe, 
all in their spare time. The problem is not that they don't know how to 
produce solid code.

The real problem is a lack of resources. There are only so many 
volunteers, who can only contribute so much time and energy. They can't 
produce perfect code on a perfect schedule. So instead they use a 
utilitarian release schedule: they ship whenever a release would 
produce the greatest good for the greatest number of PHP users.

If a small minority of php users fall through the cracks, it's to be 
expected. If they can't or won't fix it themselves, and they are rude 
when asking somebody else to do it, it's not suprising that the 
response isn't terribly enthusiastic.

Colin

---------------------------------------------
Colin Putney         [email protected]
Whistler Networks    http://www.whistler.net/