Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 44146 invoked from network); 4 Sep 2008 14:41:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Sep 2008 14:41:16 -0000 Received: (qmail 41130 invoked by uid 500); 4 Sep 2008 14:41:14 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 40945 invoked by uid 500); 4 Sep 2008 14:41:13 -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 40934 invoked by uid 99); 4 Sep 2008 14:41:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Sep 2008 07:41:13 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com designates 209.85.217.15 as permitted sender) Received: from [209.85.217.15] (HELO mail-gx0-f15.google.com) (209.85.217.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Sep 2008 14:40:14 +0000 Received: by gxk8 with SMTP id 8so6364374gxk.14 for ; Thu, 04 Sep 2008 07:40:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=/lO/uG+KX1hkRe7isbQmaEjMOytVifcG+dsuotYCpTk=; b=H/gMcUclZj1ZS8wRZgUgKTkn/T9aqfdZY/SFV5zISTipsFQl4DMcfQmGNVMUlV2BrT qo91+hbHX4mJTmPjFt9YxdXhgNkJcBI2cf3F7Hh6gbYiCr7nU6AewQRrLnclYO0qke+m xXfh119rO0gwjyxMoKIZsRFfZkR8FGVi4S7pI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=MY1BsVvG4RhCd5mYX7CbC/lckbfxpxBl2/ZcY6XCPtTSn0J4QHUTMwGiLj63QUXJWR Ge9ME5tmWHQ9wuh/g+hn+ZyAbxwoZA46/9EJ0zXJFMG7J4A4eumtAR5IDcxnG8O16sVk MhOryl2oXHhksA/k6JJAhML8ePayYQOo8d0Qs= Received: by 10.150.215.17 with SMTP id n17mr4669891ybg.222.1220539245400; Thu, 04 Sep 2008 07:40:45 -0700 (PDT) Received: by 10.150.138.18 with HTTP; Thu, 4 Sep 2008 07:40:45 -0700 (PDT) Message-ID: <3a73c17c0809040740v1976decelf15ee2abff487ca9@mail.gmail.com> Date: Thu, 4 Sep 2008 15:40:45 +0100 From: "Gary Tully" To: dev@activemq.apache.org Subject: Re: time for a 5.2 release I think. In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3a73c17c0809040721j67180b4t8b2062c49a20c6fd@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ok thanks, will do the jira release first. so it is kind of an 'auto' roadmap, everything will be fixed in the next release until it is not. I guess this is the easiest way to keep things rolling. A default of fix version unknown would require explicit roadmap management and lots more work. 2008/9/4 Guillaume Nodet : > What I usually do is to release in JIRA before the actual release (you > can always change the date later in jira) so that I can build the > release notes and download page using the informations in jira. As > James said, when you release in jira, all the versions not fixed are > put under the next version to be released. > And I disagree that only resolved issues should have a fix version, as > this is the way you can track a roadmap ... > > On Thu, Sep 4, 2008 at 4:27 PM, James Strachan wrote: >> 2008/9/4 Gary Tully : >>> I want to do a 5.2 release. >> >> Yay! >> >>> There are 189 open issues with a fix >>> version of 5.2 [1]. As these issues show up in the release notes[2], I >>> think they should all be marked as fix version 'unknown' until they >>> get resolved on trunk, in which event they again get a fix version. Am >>> thinking that only resolved issues should have a fix version. >>> >>> comments? >> >> Yeah - when you actually do the release in JIRA, it moves all issues >> with a fix for 5.2 to the next available release. So you might as well >> just wait until we vote on the distro, then let JIRA do all the hard >> work for you >> -- >> James >> ------- >> http://macstrac.blogspot.com/ >> >> Open Source Integration >> http://open.iona.com >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ >