Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 72621 invoked from network); 14 Sep 2005 08:46:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Sep 2005 08:46:27 -0000 Received: (qmail 72494 invoked by uid 500); 14 Sep 2005 08:46:25 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 71961 invoked by uid 500); 14 Sep 2005 08:46:24 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 71948 invoked by uid 99); 14 Sep 2005 08:46:23 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Sep 2005 01:46:23 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [65.77.211.84] (HELO www2.kc.aoindustries.com) (65.77.211.84) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Sep 2005 01:46:34 -0700 Received: from fo2.kc.aoindustries.com (www2.kc.aoindustries.com [65.77.211.84]) by www2.kc.aoindustries.com (8.13.1/8.13.1) with ESMTP id j8E8kLf9026403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 14 Sep 2005 03:46:21 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by fo2.kc.aoindustries.com (8.13.1/8.13.1/Submit) id j8E8kKRj026357 for dev@cocoon.apache.org; Wed, 14 Sep 2005 03:46:20 -0500 X-Authentication-Warning: fo2.kc.aoindustries.com: indexgeo set sender to crossley@apache.org using -f Date: Wed, 14 Sep 2005 18:46:13 +1000 From: David Crossley To: dev@cocoon.apache.org Subject: Re: Shall we switch to Jira? Message-ID: <20050914084613.GA9350@igg.indexgeo.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Bertrand Delacretaz wrote: > Arje Cahn a ?crit : > >...How can I get Bugzilla to tell me what issues are scheduled to be > >fixed for the next release?.. > > Very easy: define an issue which represents the next release, and make > it dependent on all issues that must be fixed. I use it all the time, > with multiple levels to build a tree of dependencies, and it works > great. We used to do that at Cocoon. Not sure if it is still. http://wiki.apache.org/cocoon/ProjectManagement e.g. http://issues.apache.org/bugzilla/showdependencytree.cgi?id=25320 However, those sets of queries are only useful if we actively manage the issue base and do the linking and classifying and fix-for-version and stuff. Exactly the same will apply in Jira. So i don't care which issue tracker we use. -David