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 ekoneil@gmail.com designates
 64.233.184.206 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=jDy/7aVLNikopkUv+6w9QJYo4FAP75qPllScMORIvv6WHNCFbFwW7/JoyLmTVQwNNP6ex6Kro0m2TVmkfvC3D3YcjP9B1gDJoxaJwyWk8DrFCf1fo1uBoNKp0YWYLeFy6Qh5FjeO6SA0A/sYswREOT1Abi+DURT8JW87dVzv1Sc=
Message-ID: <e9ac835405061509264ff08296@mail.gmail.com>
Date: Wed, 15 Jun 2005 10:26:47 -0600
From: Eddie ONeil <ekoneil@gmail.com>
Reply-To: Eddie ONeil <ekoneil@gmail.com>
To: Beehive Developers <beehive-dev@incubator.apache.org>
Subject: Re: [vote] cleaning up jira by renaming v1 to v1m1
In-Reply-To: <e9ac83540506141604f69da97@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <e9ac835405061317323f668f33@mail.gmail.com>
	 <3e7c9d1505061409444b96bde1@mail.gmail.com>
	 <e9ac83540506141604f69da97@mail.gmail.com>

All--

  This is now complete (JIRA rocks!).  I also made a couple of other
JIRA changes:

- changed the v1 alpha, v1 beta, v1 m1 releases to be 'released' which
means that they show up differently in the select boxes when
manipulating bugs
- added a 'system controls' category under which the JDBC, JMS, EJB,
and web service control bugs should be filed
- recreated the V1 release which should now be empty

  So, I've left all bugs in TBD as we probably need to be selective
about the bugs we're going to fix before a 1.0 (Incubating) release.=20
Also, anything fixed since V1m1 can be brought back and marked V1.

  We might consider, in the long run, having a 'v.next' version so
that JIRA doesn't imply the release # of the subsequent release.  This
would make it easier to change a release name since we can always just
mrege releases in JIRA.  But, the bug system is setup for moving
toward 1.0 (Incubating) now.

Eddie


On 6/14/05, Eddie ONeil <ekoneil@gmail.com> wrote:
>   Strikes me as though there's general concensus that this is the
> right thing to do.  If you've got an opinion in the next 18 hours or
> so, feel free to say so.
>=20
>   We'll leave this open till tomorrow around noon eastern after which
> I'll attempt to merge the versions.
>=20
>   Hopefully, that doesn't result in JIRA sending a bunch of bug mail.
>=20
>   :)
>=20
> Eddie
>=20
>=20
> On 6/14/05, Kyle Marvin <kylemarvin@gmail.com> wrote:
> > +1
> >
> > On 6/13/05, Eddie ONeil <ekoneil@gmail.com> 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 provid=
e
> > > an explanation and add a new moniker for what to actually call 1.0
> > > that isn't "V1".  :)
> > >
> >
>