Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65804 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53400 invoked from network); 13 Feb 2013 18:02:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Feb 2013 18:02:57 -0000 Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 config.schlueters.de Received: from [217.114.211.66] ([217.114.211.66:35314] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B6/88-03493-055DB115 for ; Wed, 13 Feb 2013 13:02:56 -0500 Received: from [192.168.2.20] (ppp-88-217-64-14.dynamic.mnet-online.de [88.217.64.14]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id AB8A665C0E; Wed, 13 Feb 2013 19:02:53 +0100 (CET) To: Lars Strojny Cc: PHP internals list In-Reply-To: <9D7F4F72-FB97-4606-9AA5-10C3C6D3D467@strojny.net> References: <1360771381.2694.24.camel@guybrush> <9D7F4F72-FB97-4606-9AA5-10C3C6D3D467@strojny.net> Content-Type: text/plain; charset="UTF-8" Date: Wed, 13 Feb 2013 19:03:48 +0100 Message-ID: <1360778628.2694.33.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Github pull request management From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Wed, 2013-02-13 at 18:37 +0100, Lars Strojny wrote: > Hi Johannes, > > quick question: does it automatically open bug reports for each PR? No, for two reasons: A. Github provides no good notification mechanism for that, we'd have to pull periodically and match it and so on B. Many requests are written after bugs were opened, if it would open bugs automatically we'd have quite a few duplicates and discussion in three places (initial analysis on initial report, review discussion at github, final discussion at the new bug) All this feature currently does is providing a "structured" (relational database model, yay) way to link from a bug report to github. I'm happy about any improvements being done, though (part of pushing this is my hope to motivate some people to think about possibilities and add better things) johannes