Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29921
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.166.183 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=tGndB3mpmOrNO+wv6sRgTdXB6pHgNfyjVFGJlFNZ3U1x08fw2AegL9HUlcMaBIRfPcL6aOzjPV4o378m38/ppFJIBCdcZhiAN3bnAfJM2/FCZhX5nO0gSygoNAK8WFKI8u7thj2VciJnYQqaFI5BOMu7EgnL86fF0nxbGIwUKt0=
Message-ID: <4e89b4260705291810n46c89723k4059bf1d565b229c@mail.gmail.com>
Date: Tue, 29 May 2007 21:10:31 -0400
To: "Steph Fox" <steph@zend.com>
Cc: internals <internals@lists.php.net>
In-Reply-To: <01ab01c7a24f$27afd7a0$39dc2f52@foxbox>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4e89b4260705280856t47429e54ofcc182e02a6627e5@mail.gmail.com>
	 <00e801c7a150$d1e15690$39dc2f52@foxbox>
	 <4e89b4260705281205y50baab0k5ea109876c3c2231@mail.gmail.com>
	 <08e901c7a1a1$192c78e0$39dc2f52@foxbox>
	 <4e89b4260705291658j554f7fcar5bf6876d4b0fdb4d@mail.gmail.com>
	 <01ab01c7a24f$27afd7a0$39dc2f52@foxbox>
Subject: Re: [PHP-DEV] better changeset tracking
From: kingwez@gmail.com ("Wez Furlong")

On 5/29/07, Steph Fox <steph@zend.com> wrote:
> This could work, except of course we don't have any such thing as 'a
> maintenance ticket' or a way to set priority to 'merge'. It's kind of the
> opposite way around to the way the PHP bug system works... and it probably
> would be a pain to have it as part of an open system (in the sense that
> users can add to it)

I don't see why we can't just add a field or two to the existing
database to cater to this--we've got the source ;-).
It's much simpler to have one source of ticket numbers--it's then very
clear to everyone where you go to create and maintain tickets as well
as where you go to read up on them.

Personally, I find it quite a pain to have to look in both the pecl
and php bug databases to track bugs for PDO; I'd like to avoid adding
to that pain by having yet another set of ticket numbers to reference.

We can solve the problem with peons and serfs adding to the db by
using authentication, just like we do now for the developer aspects to
the bugs db.

> It's the difference between a controlled environment and open source....
> but I can see it working if the 'per milestone' route is taken, that's a
> good idea. Anyone with QA/bugs karma care to intervene at this point?

Well, what we're really discussing here is adding some enforced
controls to our open source development.  My suggestion is a pretty
light-weight modification to what we have now, and doesn't intrude
terribly on getting stuff done.

- add a maintenance category to bug db
- add merge status to bug db
- add commit hook to detect a bug number in the commit log.
- add some method of automatically commenting on bug reports with the
commit message and urls to the diffs

that's the basic bit to facilitate manual review.

The next step from there is writing that cron job to analyze tickets
with missing merge activity.  This is easily the hardest part to
implement; I'd suggest doing that last--nothing else depends on it
being there, it's just a convenience to avoid manual review of
everything, and we might find that we don't need it after all if we're
good at respecting the merge status.

--Wez.