Mailing-List: contact beehive-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Developers" <beehive-dev@incubator.apache.org>
Received-SPF: pass (hermes.apache.org: domain of bche@redhat.com designates
 66.187.233.31 as permitted sender)
Message-ID: <42AEF7FB.5020909@redhat.com>
Date: Tue, 14 Jun 2005 11:30:03 -0400
From: Bryan Che <bche@redhat.com>
User-Agent: Mozilla Thunderbird  (X11/20050322)
MIME-Version: 1.0
To: Beehive Developers <beehive-dev@incubator.apache.org>
Subject: Re: [vote] cleaning up jira by renaming v1 to v1m1
References: <e9ac835405061317323f668f33@mail.gmail.com>
In-Reply-To: <e9ac835405061317323f668f33@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

+1

Bryan

Eddie ONeil wrote:
> All--
> 
>   In the course of releasing Beehive 1.0 v1m1, we overloaded the use
> of the "V1" release Fix Version in JIRA to really mean "V1m1".  The
> result is that we've now stolen the "V1" release version from the bug
> tracking system making it harder to explain how to file / fix bugs
> going forward.
> 
>   It appears that JIRA has a "merge" option for releases, and given
> this, I believe that we can take the bugs currently with a "Fix
> Version" in "V1" and reassign them to a new release "V1m1".
> 
>   This would allow us to use the "V1" moniker for work that is going
> on as we actually move toward a 1.0 (Incubating) release.  We could
> then bring bugs back from TBD that will be fixed before 1.0
> 
>   So, I'd like to suggest that we rename the "V1" bugs to "V1m1" and
> use "V1" to mean the bugs going forward en route to 1.0.  Please vote!
> 
> Eddie
> 
> Vote:
> [+1] Yes, push the "V1" bugs back to "V1m1"
> [0]  Abstain / not sure / don't care.
> [-1] No, leave the bugs in "V1".  If you vote this way, please provide
> an explanation and add a new moniker for what to actually call 1.0
> that isn't "V1".  :)