You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by Carlin Rogers <ca...@gmail.com> on 2006/11/04 00:22:21 UTC

magic to add another adding a new "Released Version" for Beehive in JIRA

Hey Eddie,

Do you usually create the new "Released Version" fields for Beehive in
JIRA or is this something that other JIRA users can do? I was
wondering about the process to add "1.0.2" to JIRA and moving the
"Fixed for" bugs from vnext over to 1.0.2. I could then go back and do
a little clean up as a couple of the bugs and improvements slated for
vnext are not going to make the 1.0.2 release and should just stay as
vnext.

Let me know how I can help with this.

Thanks,
Carlin

Re: magic to add another adding a new "Released Version" for Beehive in JIRA

Posted by Carlin Rogers <ca...@gmail.com>.
OK. Thanks for taking care of that.

Carlin

On 11/3/06, Eddie O'Neil <ek...@gmail.com> wrote:
>   I'll take care of this over the weekend -- it's pretty easy with the
> appropriate JIRA karma.  This will also move all of the bugs fixed in
> "v.next" into the 1.0.2 bucket.
>
>   Good call -- I'd forgotten about this -- it's been so long.  :)
>
> Eddie
>
> On 11/3/06, Carlin Rogers <ca...@gmail.com> wrote:
> > nice, confusing subject line... must be the end of the week. ;-)
> >
> > On 11/3/06, Carlin Rogers <ca...@gmail.com> wrote:
> > > Hey Eddie,
> > >
> > > Do you usually create the new "Released Version" fields for Beehive in
> > > JIRA or is this something that other JIRA users can do? I was
> > > wondering about the process to add "1.0.2" to JIRA and moving the
> > > "Fixed for" bugs from vnext over to 1.0.2. I could then go back and do
> > > a little clean up as a couple of the bugs and improvements slated for
> > > vnext are not going to make the 1.0.2 release and should just stay as
> > > vnext.
> > >
> > > Let me know how I can help with this.
> > >
> > > Thanks,
> > > Carlin
> > >
> >
>

Re: magic to add another adding a new "Released Version" for Beehive in JIRA

Posted by Eddie O'Neil <ek...@gmail.com>.
  I'll take care of this over the weekend -- it's pretty easy with the
appropriate JIRA karma.  This will also move all of the bugs fixed in
"v.next" into the 1.0.2 bucket.

  Good call -- I'd forgotten about this -- it's been so long.  :)

Eddie

On 11/3/06, Carlin Rogers <ca...@gmail.com> wrote:
> nice, confusing subject line... must be the end of the week. ;-)
>
> On 11/3/06, Carlin Rogers <ca...@gmail.com> wrote:
> > Hey Eddie,
> >
> > Do you usually create the new "Released Version" fields for Beehive in
> > JIRA or is this something that other JIRA users can do? I was
> > wondering about the process to add "1.0.2" to JIRA and moving the
> > "Fixed for" bugs from vnext over to 1.0.2. I could then go back and do
> > a little clean up as a couple of the bugs and improvements slated for
> > vnext are not going to make the 1.0.2 release and should just stay as
> > vnext.
> >
> > Let me know how I can help with this.
> >
> > Thanks,
> > Carlin
> >
>

Re: magic to add another adding a new "Released Version" for Beehive in JIRA

Posted by Carlin Rogers <ca...@gmail.com>.
nice, confusing subject line... must be the end of the week. ;-)

On 11/3/06, Carlin Rogers <ca...@gmail.com> wrote:
> Hey Eddie,
>
> Do you usually create the new "Released Version" fields for Beehive in
> JIRA or is this something that other JIRA users can do? I was
> wondering about the process to add "1.0.2" to JIRA and moving the
> "Fixed for" bugs from vnext over to 1.0.2. I could then go back and do
> a little clean up as a couple of the bugs and improvements slated for
> vnext are not going to make the 1.0.2 release and should just stay as
> vnext.
>
> Let me know how I can help with this.
>
> Thanks,
> Carlin
>