Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 9793 invoked from network); 24 Jan 2008 13:59:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Jan 2008 13:59:43 -0000 Received: (qmail 95729 invoked by uid 500); 24 Jan 2008 13:59:33 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 95696 invoked by uid 500); 24 Jan 2008 13:59:33 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 95687 invoked by uid 99); 24 Jan 2008 13:59:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jan 2008 05:59:33 -0800 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [192.18.6.21] (HELO gmp-eb-mail-1.sun.com) (192.18.6.21) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jan 2008 13:59:05 +0000 Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m0ODx8hA004462 for ; Thu, 24 Jan 2008 13:59:10 GMT Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JV500701IUI7Y00@fe-emea-09.sun.com> (original mail from Dyre.Tjeldvoll@Sun.COM) for derby-dev@db.apache.org; Thu, 24 Jan 2008 13:59:08 +0000 (GMT) Received: from khepri32.sun.com ([129.159.112.244]) by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JV5008PTIUJ7110@fe-emea-09.sun.com> for derby-dev@db.apache.org; Thu, 24 Jan 2008 13:59:08 +0000 (GMT) Date: Thu, 24 Jan 2008 14:59:07 +0100 From: Dyre.Tjeldvoll@Sun.COM Subject: Closing old jiras Sender: Dyre.Tjeldvoll@Sun.COM To: Derby Development Message-id: MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (usg-unix-v) X-Virus-Checked: Checked by ClamAV on apache.org Hi everybody, I know that according to the official workflow for Derby: http://db.apache.org/derby/DerbyBugGuidelines.html#%22Close%22+your+bug+once+it+is+%22Resolved%22 the reporter is supposed to close the issue: "As the submitter of a bug, it is your responsibility to verify a bug fix and "Close" the issue." As some of you may have noticed, I violated this rule today and bulk-closed issues that were resolved, but had not been updated in the last 12 months. I considered making a "Could this be closed now" comment, but decided that the extra mail traffic wasn't worth it. Unfortunately there are another 135 resolved issues that have not been updated in the last 6 months: http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&updated%3Abefore=24%2FJul%2F07&status=5&sorter/field=issuekey&sorter/order=DESC And 241 that have not been updated this year: http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&updated%3Abefore=31%2FDec%2F07&status=5&sorter/field=issuekey&sorter/order=DESC Perhaps we need to amend the workflow rules with a time limit, so that resolved issues can be automatically closed? Or should someone (like the release manager) perodically remind people that they should close issues they have reported? I guess it is inevitable that some issue-reporters leave the community so there will always be some bulk-closing now and then. But surprisingly many of the resolved issues are actually reported by people who are still active in the community. So perhaps the workflow rules do need to be revised...? -- dt