Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 71270100F0 for ; Sat, 19 Apr 2014 14:11:47 +0000 (UTC) Received: (qmail 97633 invoked by uid 500); 19 Apr 2014 14:11:46 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 97569 invoked by uid 500); 19 Apr 2014 14:11:46 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 97557 invoked by uid 99); 19 Apr 2014 14:11:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Apr 2014 14:11:46 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of cjnolet@gmail.com designates 209.85.213.171 as permitted sender) Received: from [209.85.213.171] (HELO mail-ig0-f171.google.com) (209.85.213.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Apr 2014 14:11:41 +0000 Received: by mail-ig0-f171.google.com with SMTP id c1so421041igq.16 for ; Sat, 19 Apr 2014 07:11:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=e+bDbob5YNoQ9qXxksqUruXJ1TAtQxMPV92VeTZNngM=; b=e43zG6LFF1Je94DAsxEUA033aAW7mjI/QKZoFep4P7R0p7QIjhNMWbrLznLVgyu5Wd chglv90lrQb/e2R4s/TdbGdS4XRFI4P0VexnHluHOdkt96BcshwIGeK1UfCT0Q4g4r9D jm2/x/aitM8oTiwR/S9vEnAPKy7qSN1mIs6VgPB2AC6x2hxl/vYFEOMO6eCa5YzSiJ1l JwN9Gtk0q9TC82A07E5B6BuGbnhU7bKtQpWSnCgtnYwTNTFyzAF9CaZXxIlZqUmYnGF0 /27qIDUGiKWzckAxi2nWVsLufKGaH/7jAghjBqnU+V6Vqzv1mz8ss93fdE1rcRnTXznZ wa/A== MIME-Version: 1.0 X-Received: by 10.50.61.142 with SMTP id p14mr10741745igr.12.1397916678975; Sat, 19 Apr 2014 07:11:18 -0700 (PDT) Received: by 10.64.11.133 with HTTP; Sat, 19 Apr 2014 07:11:18 -0700 (PDT) In-Reply-To: References: Date: Sat, 19 Apr 2014 10:11:18 -0400 Message-ID: Subject: Re: 551 JIRA Tickets Over 2 Years Old From: Corey Nolet To: "dev@accumulo.apache.org" Content-Type: multipart/alternative; boundary=047d7bdca30013787204f765d73a X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdca30013787204f765d73a Content-Type: text/plain; charset=UTF-8 Some of these tickets still look like very valid feature/integration requests that would still be reasonable to have. See ACCUMULO-74, ACCUMULO-143, ACCUMULO-136, ACCUMULO-211, ACCUMULO-483, ACCUMULO-490, ACCUMULO-508 On Sat, Apr 19, 2014 at 9:54 AM, Mike Drob wrote: > Deleting tickets is a no-no, but flagging them is certainly fine. > On Apr 19, 2014 12:03 AM, "David Medinets" > wrote: > > > Opps. Sorry, I did my filtering badly. There are 68 tickets over 2 years > > old. > > > > > > > https://issues.apache.org/jira/browse/ACCUMULO-18?jql=project%20%3D%20ACCUMULO%20AND%20status%20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22%29%20AND%20created%20%3C%3D%20-104w%20ORDER%20BY%20key%20ASC > > > > > > > > > > On Sat, Apr 19, 2014 at 12:01 AM, David Medinets > > wrote: > > > > > > > > > > > https://issues.apache.org/jira/browse/ACCUMULO-551?jql=project%20%3D%20ACCUMULO%20AND%20created%20%3C%3D%20-104w%20ORDER%20BY%20key%20DESC > > > > > > Is there a technique we can use to curate old tickets? Would anyone > mind > > > if I review them and nominate tickets for closure? I can add a message > > and > > > delete any tickets that don't provoke a response. How useful are > tickets > > > that are two years old? > > > > > > --047d7bdca30013787204f765d73a--