From owner-freebsd-python@FreeBSD.ORG Tue Sep 15 09:08:54 2009 Return-Path: <owner-freebsd-python@FreeBSD.ORG> Delivered-To: freebsd-python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86C901065697; Tue, 15 Sep 2009 09:08:54 +0000 (UTC) (envelope-from david@vizion2000.net) Received: from dns1.vizion2000.net (77-99-36-42.cable.ubr04.chap.blueyonder.co.uk [77.99.36.42]) by mx1.freebsd.org (Postfix) with ESMTP id 45AD88FC43; Tue, 15 Sep 2009 09:08:54 +0000 (UTC) Received: by dns1.vizion2000.net (Postfix, from userid 1001) id 5F39E34D44F; Tue, 15 Sep 2009 10:08:52 +0100 (BST) From: David Southwell <david@vizion2000.net> Organization: Voice & Vision To: freebsd-ports@freebsd.org Date: Tue, 15 Sep 2009 10:08:52 +0100 User-Agent: KMail/1.12.1 (FreeBSD/7.2-RELEASE-p3; KDE/4.3.1; amd64; ; ) References: <200909150954.10209.david@vizion2000.net> In-Reply-To: <200909150954.10209.david@vizion2000.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200909151008.52311.david@vizion2000.net> Cc: miwi@freebsd.org, James Chang <james.technew@gmail.com>, freebsd-ports-bugs@dns1.vizion2000.net, freebsd-python@freebsd.org Subject: Re: Premature closure of PRs X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python> List-Post: <mailto:freebsd-python@freebsd.org> List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 15 Sep 2009 09:08:54 -0000 > I want to understand why bug reports get closed prematurely and without any > discussion with the original person submitting the report. > > For example I submitted PR today in connection with a bug I originally > reported to both the ports and the python lists last week. When there was > no immediate fix I then submitted a PR this morning at was submitted: > > Tue Sep 15 08:10:02 UTC 2009 > > It was closed 8 minutes later without further query: > > Closed-Date: Tue Sep 15 08:18:07 UTC 2009 > > Despite the fact there had been a posting on both the ports and python > lists by James Chang which was distributed to the lists at > > Tue, 15 Sep 2009 06:48:37 +0000 (UTC) > > I then attempted to Submit a Follow up to include Chang's report only to > find that the PR had been prematurely closed simply because the maintainer > assumed that as he could not replicate it the report must be unfounded. > > Last-Modified: Tue Sep 15 08:18:07 UTC 2009 > > Can we please have the system modified so that reports are not closed until > the submitter has had an opportunity to review the reasons and comment. > > Lastly How does one get a closed PR re-opened? > > Yrs frustrated > David Southwell ps the PR link is: http://www.freebsd.org/cgi/query-pr.cgi?pr=138835 (ports/138835: Python compile failure) >