Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32032
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mysql.com from 213.136.52.68 cause and error)
Message-ID: <46DD575F.6070004@mysql.com>
Date: Tue, 04 Sep 2007 15:02:23 +0200
Organization: MySQL AB
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20061211 SeaMonkey/1.0.7
MIME-Version: 1.0
To: BuildSmart <buildsmart@daleenterprise.com>
CC: PHP Developers Mailing List <internals@lists.php.net>
References: <20CECB37-7174-498C-85EA-A862923E594D@daleenterprise.com> <1188809931.3317.0.camel@localhost.localdomain> <C0C21D32-D496-49E1-92E0-A860E866CAF4@daleenterprise.com> <46DC0FFC.9040403@mysql.com> <4AA18585-8F96-4A6E-A990-E5FAD0DECA7E@daleenterprise.com> <46DC5EB6.8020805@mysql.com> <925E216E-7B66-4D68-956B-042C1422FE90@daleenterprise.com> <fe05d1540709040224l5c2251b5p3e45db9cab77c498@mail.gmail.com> <0C276E60-3C18-4A4A-943A-DC58A05FD557@daleenterprise.com>
In-Reply-To: <0C276E60-3C18-4A4A-943A-DC58A05FD557@daleenterprise.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] buildconf and the generated configure script for PHP6
 is faulty [the fix].
From: hartmut@mysql.com (Hartmut Holzgraefe)

Dear Mr BuildSmart

BuildSmart wrote:
> SInce I didn't consider it a bug but rather a minor error of importance=
,=20

just out of curiosity: how do you define "bug" if not as "any error"?

> I thought it would best be handled by making the maintainers aware of=20
> the issue since the fix is relatively simple and provided to avoid the =

> filing of bug reports which would have occurred.

this is wrong in several ways:

  - your original posting did not include the actual fix but
    only what should change in the generated configure file

    the actual fix was only in your mail of 12:10 today.
    giving you the benefit of the doubt i'd assume for now
    that it was attached to the original message, too, but
    got stripped, this would not have happened with a bug
    report though

  - the bug database is not only a todo list, it is also
    a repository of bugs fixed in the past. e.g. have you
    noticed the duplicate detection when filing a bug?
    with a bug fixed out of band without involving the
    bugs db duplicate detection can't kick in on new bug
    reports

  - changelog entries usually refer to a bug number,
    having them point to a mail archive instead would
    be inconsistant and so bad

  - same for commit messages ... add to this that it is
    easy to refer to a bug number but way less so to
    refer to a distinct email

So working around the bug system is not a shortcut,
it actually generates *more* work in the long run.

The bug system is there to be *used*, not to be
circumvented.

If you had submitted your finding as a bug report
with proper how-to-reproduce instructions (which
your original message did not have, what you wrote
there was way to vague) and also with your patch
to ext/standard/config.m4 things would probably
been handled just fine already. Look what mess you
caused instead ... :(

--=20
Hartmut Holzgraefe, Principal Support Engineer
               .
Discover new MySQL Monitoring & Advisory features at:
http://www.mysql.com/products/enterprise/whats_new.html

Hauptsitz: MySQL GmbH, Dachauer Str.37, 80335 M=FCnchen
Gesch=E4ftsf=FChrer: Kaj Arn=F6 - HRB M=FCnchen 162140