Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=earthlink.net;
  b=dbXuQGLthRu8S6naGSwi85JKQKq+9In/C9FFxPd82Tcuz898G/I8VRxP9dpB11Eh;
  h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Message-ID: <4888D234.7010904@earthlink.net>
Date: Thu, 24 Jul 2008 15:04:20 -0400
From: Joe Bohn <joe.bohn@earthlink.net>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: JIRA versions 2.0.x & 2.1.x
References: <48874387.7060705@earthlink.net> <4888CFD0.30702@apache.org>
In-Reply-To: <4888CFD0.30702@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Donald Woods wrote:
> Thought these were to be used to keep everything out of a generic Future 
> bucket, but it has never worked, so +1 to removing them.
> 
> BTW - Shouldn't the Fix Version field remain blank until someone either 
> starts working on the issue or code is integrated into svn?
> 

I think there are different opinions on the Fix Version field.  We've 
been using it in the past to "target" fixes for a particular release 
before a JIRA is resolved.  I guess my opinion would be to leave it 
blank until there is some reason to mark for a perspective release. 
When the issue is eventually resolved it should be updated to reflect 
the actual version(s) that will include the fix once released.

Joe


> 
> -Donald
> 
> 
> Joe Bohn wrote:
>> What is the value of JIRA versions 2.0.x and 2.1.x?  Having these 
>> makes it difficult to track changes per release.  For example, when a 
>> JIRA is resolved in branches/2.1 intended for a 2.1.2 release - we 
>> should mark the JIRA as fixed in the not-yet-released 2.1.2.  However, 
>> it is all too easy to choose 2.1.x instead of 2.1.2.  The problem is 
>> that 2.1.x JIRAs won't show up in reports we generate for release 
>> notes for 2.1.2.
>>
>> I'd like to remove the *.x versions from our JIRA project so that 
>> people will be encouraged to include the specific version as the fix 
>> version. I'll work through the JIRAs and cleanup references prior to 
>> removal (I have to do this anyway for 2.1.2).
>>
>> Any objections?
>>
>>
>> Joe
>>