Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 93290 invoked from network); 7 Jul 2006 15:21:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Jul 2006 15:21:52 -0000 Received: (qmail 15034 invoked by uid 500); 7 Jul 2006 15:21:51 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 14456 invoked by uid 500); 7 Jul 2006 15:21:49 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 14445 invoked by uid 99); 7 Jul 2006 15:21:49 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jul 2006 08:21:49 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of flamefew@gmail.com designates 64.233.182.184 as permitted sender) Received: from [64.233.182.184] (HELO nf-out-0910.google.com) (64.233.182.184) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jul 2006 08:21:41 -0700 Received: by nf-out-0910.google.com with SMTP id p46so629826nfa for ; Fri, 07 Jul 2006 08:18:59 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YfIOEZDsSh9iTJ6Ai5VxTuW97DpECPbmbMrGcg06ijwzgzHVCswOQ4uk+0IrFMrXaVJBNUqGfMMuy4S5tMBihoZjfMtOM/T1C5RKDROVw1yQUe4KEEKjHBeBhAzZ9Yy5aaidqq2DkVHnpPmvz2O9oqvA9wrxksjqHn8nPuttnDA= Received: by 10.78.160.2 with SMTP id i2mr736055hue; Fri, 07 Jul 2006 08:18:58 -0700 (PDT) Received: by 10.78.137.11 with HTTP; Fri, 7 Jul 2006 08:18:58 -0700 (PDT) Message-ID: <31cc37360607070818w1b8d008fj692ff217eee76175@mail.gmail.com> Date: Fri, 7 Jul 2006 08:18:58 -0700 From: "Henri Yandell" To: "Jakarta Commons Developers List" Subject: Re: Jira usage In-Reply-To: <8a81b4af0607062136h6acd818bsb5898b3dc3b5f3fe@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <31cc37360607061146v7c2d910bi7069bac9e671902d@mail.gmail.com> <8a81b4af0607062136h6acd818bsb5898b3dc3b5f3fe@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 7/6/06, Phil Steitz wrote: > > One more thing along these lines. I can't remember where I saw an > intelligent explanation of how we should use "closed" vs. "resolved" > in Jira. I guess a reasonable approach given the above strategy would > be to wait to close until the fix version is actually released, unless > the closing is "won't fix" or "invalid" (in which case, there is no > fix version). Is that right? Jorg has the correct way I think - resolve and then worry about closing in a release, but because there's no bulk-close mechanism I tend towards Craigs view of seeing RESOLVED and CLOSED as being equal for open source projects. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org