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: domain of shivahr@gmail.com designates
 209.85.198.229 as permitted sender)
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:references;
        b=tBOzcAd0CdnnP5UeAIalnJcumJ3ZBPFu/06YnQXlWYvWFL/wX15x+Ml1MZyzS327z5
         8lzUPRfEJIpii8Otku5LN2mskTVQ2pibDdy/bHkwrVFQQVlo7xxIFvXK9cfpp/A7paRG
         NDX6brvwcOnZwTxCB0GDQlpaF9WyFg1Vk0Z0w=
Message-ID: <5da94e5a0807232244j39f62d8ai1405c06ca96bd7d0@mail.gmail.com>
Date: Thu, 24 Jul 2008 11:14:45 +0530
From: "Shiva Kumar H R" <shivahr@gmail.com>
To: dev@geronimo.apache.org
Subject: Re: JIRA versions 2.0.x & 2.1.x
In-Reply-To: <48874387.7060705@earthlink.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_76262_9128025.1216878285104"
References: <48874387.7060705@earthlink.net>

------=_Part_76262_9128025.1216878285104
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

+1. I think we should do this in Geronimo Eclipse Plug-in (GEP) too.

On Wed, Jul 23, 2008 at 8:13 PM, Joe Bohn <joe.bohn@earthlink.net> 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
>


-- 
Thanks,
Shiva

------=_Part_76262_9128025.1216878285104
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">+1. I think we should do this in Geronimo Eclipse Plug-in (GEP) too.<br><br><div class="gmail_quote">On Wed, Jul 23, 2008 at 8:13 PM, Joe Bohn &lt;<a href="mailto:joe.bohn@earthlink.net">joe.bohn@earthlink.net</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">What is the value of JIRA versions 2.0.x and 2.1.x? &nbsp;Having these makes it difficult to track changes per release. &nbsp;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 <a href="http://2.1.2." target="_blank">2.1.2.</a> &nbsp;However, it is all too easy to choose 2.1.x instead of <a href="http://2.1.2." target="_blank">2.1.2.</a> &nbsp;The problem is that 2.1.x JIRAs won&#39;t show up in reports we generate for release notes for <a href="http://2.1.2." target="_blank">2.1.2.</a><br>

<br>
I&#39;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&#39;ll work through the JIRAs and cleanup references prior to removal (I have to do this anyway for 2.1.2).<br>

<br>
Any objections?<br><font color="#888888">
<br>
<br>
Joe<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Thanks,<br>Shiva
</div>

------=_Part_76262_9128025.1216878285104--