Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29607
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.139 cause and error)
Message-ID: <46515083.1020403@lsces.co.uk>
Date: Mon, 21 May 2007 08:55:47 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070222 SeaMonkey/1.1.1
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <1082866338.20070516162127@marcus-boerger.de> <464ED249.50104@zend.com> <4e89b4260705190659xee5ccf8x7be8a9b161c3196a@mail.gmail.com> <200705201052.13177.forums@jefferyfernandez.id.au> <464FEF85.1020806@lsces.co.uk> <46512711.9070504@zend.com>
In-Reply-To: <46512711.9070504@zend.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP 6 Preview
From: lester@lsces.co.uk (Lester Caine)

Stanislav Malyshev wrote:
>> I don't see ANY reason bugs should be assigned by anybody other than 
>> the person who is ACTUALLY working on it?
>> *IF* someone has time or has found a fix for a problem, THEY assign 
>> the bug to them selves and put up the fix.
> 
> Well, there's a reason - not every developer watches bugs closely. 
> Thanks to great work by Antony, there's somebody who does that, but we 
> can't realistically expect every maintainer to do that, so assigning 
> bugs is the means to alert the developer that this bug is (at least 
> potentially) in his domain.

Assigning blindly is not the right procedure. There needs to be a proper 
REFERRAL process so that other people who are working in the area are made 
aware of the problem. If the bug is flagged with the correct area or package 
name, then anybody can pick up the baton. Simply 'assigning' a bug to say Wez 
when AS HE SAYS - there are other developers - is a pointless waste of time.

>> Requests for someone to LOOK at a particular bug could be made, but 
>> the decision on assignment should only be made by the person DOING the 
>> work?
> 
> I think assignment is request to look - and if possible fix, if not - 
> one should indicate he can't accept it. Of course, as we know, in theory 
> practice follows theory, in practice it doesn't - so there are cases 
> where bugs are assigned but not really looked at.

HOW do you 'request' a group of developers look at a bug?
Personally I scan the bug summary each week to see what has popped up on my 
areas of interest ( The 'feature requests' should be killed from that !!! ) 
and that would seem to be the most productive method possible. Antony and 
others just needs to make sure that bugs are correctly classified and 
duplicates flagged and removed. There are assigned bugs there that have not 
moved in months and it would be nice to see the total number of BUGS going down.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://home.lsces.co.uk
MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Firebird Foundation Inc. - http://www.firebirdsql.org/index.php