Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <ampedal@gmail.com>) id 1R5o4a-00007Y-6h
	for bitcoin-development@lists.sourceforge.net;
	Tue, 20 Sep 2011 00:20:28 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.43 as permitted sender)
	client-ip=209.85.216.43; envelope-from=ampedal@gmail.com;
	helo=mail-qw0-f43.google.com; 
Received: from mail-qw0-f43.google.com ([209.85.216.43])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1R5o4Y-000698-VG
	for bitcoin-development@lists.sourceforge.net;
	Tue, 20 Sep 2011 00:20:28 +0000
Received: by qwm42 with SMTP id 42so17814513qwm.2
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 19 Sep 2011 17:20:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.3.70 with SMTP id 6mr106164qcm.190.1316478019879; Mon, 19
	Sep 2011 17:20:19 -0700 (PDT)
Received: by 10.229.227.137 with HTTP; Mon, 19 Sep 2011 17:20:19 -0700 (PDT)
Date: Mon, 19 Sep 2011 20:20:19 -0400
Message-ID: <CAL0fb63-zObvzirU1T6-xQnKc4=Ly2go5BBF9Q0XjqAc3o8V7A@mail.gmail.com>
From: Alex Waters <ampedal@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.3 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(ampedal[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
	0.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service
	0.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R5o4Y-000698-VG
Subject: [Bitcoin-development] Issue / Pulls timers
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 20 Sep 2011 00:20:28 -0000

I would like to propose adding timers to the pulls / issues:

https://github.com/bitcoin/bitcoin/pull/523

"From time to time a pull request will become outdated. If this occurs, and
the pull is no longer automatically mergeable; it will be closed after 15
days. This can be avoided by rebasing the commit. Pull requests closed in this
manner will have their corresponding issue labeled stagnant.

Non-bug issues with no commits will be closed after 15 days from their
last activity.
Issues closed in this manner will be labeled stale.

Requests to reopen closed pull requests and/or issues can be submitted to
QA@BitcoinTesting.org. "

This will help cut down on the abandoned / stagnant pulls and issues.
It will also focus attention on priority items, and phase out unwanted changes.

Sidenote: QA@BitcoinTesting.org is working, unlike QA@Bitcoin.org

-Alex