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=n2PRKMORMxisa9yv2nyOTBaNjXZyjpUL7jXRLtcQ2nZFoKUqw0RzkOyDpStk+dTp;
  h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Message-ID: <48874387.7060705@earthlink.net>
Date: Wed, 23 Jul 2008 10:43:19 -0400
From: Joe Bohn <joe.bohn@earthlink.net>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Geronimo Dev <dev@geronimo.apache.org>
Subject: JIRA versions 2.0.x & 2.1.x
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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