Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 74641 invoked from network); 23 Nov 2009 14:32:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Nov 2009 14:32:56 -0000 Received: (qmail 82324 invoked by uid 500); 23 Nov 2009 14:32:56 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 82263 invoked by uid 500); 23 Nov 2009 14:32:56 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 82253 invoked by uid 99); 23 Nov 2009 14:32:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Nov 2009 14:32:56 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bruce.snyder@gmail.com designates 209.85.220.213 as permitted sender) Received: from [209.85.220.213] (HELO mail-fx0-f213.google.com) (209.85.220.213) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Nov 2009 14:32:46 +0000 Received: by fxm5 with SMTP id 5so6233258fxm.8 for ; Mon, 23 Nov 2009 06:32:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=oo1ZeASn3dPTqYjiWPbaervO+TR3dM4Z6WCa9wwgz+Q=; b=X1guTdUHQKGG4Tr1CxQ8Zv+gAHgYdzeSrcG5/v8xOQ2br0SJMeg5mpcfVIXUUQvFX9 LHDuWPJcRDnTNB4h+6WqhKbf/jTlgkz8SaWfvYPSSeDtWNAfulqLw1O4tbCgdKQE1pdC ZybVwRGgJ/0+o0AEInEjgf3hSrxvRmxnrWXVc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=GOhhyvgZM1Q0xNm2Fl2E54xrzrBfzNO9yIxXhVD0WkREeF0/TMNqPguzHy/qEX8kT9 9nfGwUsdgUez033vlNFj4u861AO3fSKFYiovmsdvsthJmikv+7Ed6NXM8tJVAT2+KuTD gY5T1yR/f33Diii8ZmfSL4Tlxduaps+/OgC0U= MIME-Version: 1.0 Received: by 10.223.97.155 with SMTP id l27mr687958fan.91.1258986746145; Mon, 23 Nov 2009 06:32:26 -0800 (PST) In-Reply-To: References: <7b3355cb0911201830y5a4a7704offd1622cf38308c6@mail.gmail.com> <7b3355cb0911210832m2b85b21dxe9cc7f657df6787d@mail.gmail.com> Date: Mon, 23 Nov 2009 07:32:26 -0700 Message-ID: <7b3355cb0911230632m5ce4ad01x949e79ca6198073d@mail.gmail.com> Subject: Re: Are JIRA issue flooding your inbox? From: Bruce Snyder To: dev@activemq.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Nov 23, 2009 at 5:19 AM, Hiram Chirino wro= te: > I think a good middle ground is that we time box how long we let an > issue without a unit test sit around before it's =A0kicked. =A0If the > original reporter or another contributor has not provided a unit test > in a month, we should close it out. I agree that we should begin aging issues, especially if they don't even have steps to reproduce. If they don't even have that, then we should mark the issue as Can't Reproduce and add a comment encouraging the user to reopen the issue if they can provide steps to reproduce or even a test. It really boils down to just staying on top of the issues as they're opened and taking action to close those that are insufficient. Bruce --=20 perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=3D6-E+G-N>61E