Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29611 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29646 invoked by uid 1010); 21 May 2007 08:15:47 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 29629 invoked from network); 21 May 2007 08:15:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 May 2007 08:15:47 -0000 Authentication-Results: pb1.pair.com header.from=antony@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=antony@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender) X-PHP-List-Original-Sender: antony@zend.com X-Host-Fingerprint: 212.25.124.162 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from [212.25.124.162] ([212.25.124.162:65261] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FC/74-30777-B0551564 for ; Mon, 21 May 2007 04:15:08 -0400 Received: (qmail 1212 invoked from network); 21 May 2007 08:15:04 -0000 Received: from internal.zend.office (HELO ?127.0.0.1?) (10.1.1.1) by internal.zend.office with SMTP; 21 May 2007 08:15:04 -0000 Message-ID: <46515505.2070707@zend.com> Date: Mon, 21 May 2007 12:15:01 +0400 User-Agent: Thunderbird 2.0.0.0 (X11/20070326) MIME-Version: 1.0 To: Lester Caine CC: PHP internals 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> <46515083.1020403@lsces.co.uk> In-Reply-To: <46515083.1020403@lsces.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP 6 Preview From: antony@zend.com (Antony Dovgal) On 21.05.2007 11:55, Lester Caine wrote: >> 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. Blindly? I'm afraid you don't understand what you're talking about. There is EXTENSIONS file (in the sources root dir) which lists extensions along with their maintainers. Do you see any maintainers for PDO? No? Me neither. Then there are any maintainers for com_dotnet except Wez? Nope.. Or maybe you know any streams maintainers except Wez and Sara? Tell me. If the file is wrong and there are other maintainers for these extensions, then I've been totally blind for years, since I follow the CVS list pretty close and I can distinguish between a person committing occasional fixes and maintainers looking for the extension on a permanent basis. >> 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. Want to help me with that (or maintainers with bugs in their extensions)? I'd gladly accept both, even though bugfixes are much more welcome =) -- Wbr, Antony Dovgal