Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29846
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.82.225 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:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=oKypyWK7U8QpuiR7XAwJUEqVNrfeYfNs3W6L750zxFP4mo4alESzqBmCd8Ruqw+poB0G7Z1mD1842nOflesE8UqRQXslOHHBriC+nfM8lFuujZ7aaXnZSeShBVXm/zLATIDDzsT7Cnm9DlA2Npdt+m2K8K7cVUsFSdpt9otZ3QQ=
Message-ID: <4e89b4260705280856t47429e54ofcc182e02a6627e5@mail.gmail.com>
Date: Mon, 28 May 2007 11:56:54 -0400
To: "Ilia Alshanetsky" <ilia@prohost.org>
Cc: "Edin Kadribasic" <edin@krug.dk>, 
	"PHP Internals List" <internals@lists.php.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: better changeset tracking
From: kingwez@gmail.com ("Wez Furlong")

As a fellow busy person, I completely understand this situation.

I also recognize that we need to find a way to guarantee that patches
don't slip through the cracks and don't get lost.

I think we could do with investing a little bit of time into finding a
way to automatically review commits to see if they have been merged to
all relevant branches.   For this to be viable, we should probably
adopt the practice of explicitly referencing a bug number in all
commits (could be enforced by the commit hook); we can then analyze
the commit messages to make sure that commits referencing a particular
bug number have a corresponding set of commits in the branches, and
vice versa.

Once we have that data, we could have job that periodically (daily)
reviews the activity per bug report and sends an email reminder about
reports that have missing merge activity for longer than a week.

--Wez.

PS: We could also consider posting links to commit URLs to the
associated bug report; this is a feature I really value in our
subversion/trac repositories at OmniTI.

On 5/26/07, Ilia Alshanetsky <ilia@prohost.org> wrote:
>
> On 26-May-07, at 6:51 AM, Edin Kadribasic wrote:
>
> > Ilia, I would really like to know why you are not merging patches
> > to head?
>
> Unfortunately I don't have as much time to spend on PHP as I'd like
> and I focus my attention on the aspects of PHP I use and can tests
> using the dev environments I have. I do not have a ready PHP6
> environment and do not have time to test thing with php6 code, with
> which I do not have as much familiarity. Rather then making commits
> that may break the builds or spending hours resolving conflicts I
> focus my attention on PHP5 where fixes and improvements have tangible
> benefits to users.
>
> That said the commits are all public and if someone who is more
> familiar with php6 code then I can merge them, it would be great.
>
> Ilia Alshanetsky
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>