You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by Eddie O'Neil <ek...@gmail.com> on 2005/09/25 17:37:55 UTC
[vote] promote Beehive 1.0 rc4 to Beehive 1.0
All right, let's try this again. :)
Just uploaded installers for Beehive 1.0 rc4. It's different from
rc3 only in that it fixes the EJB control assembly problem in
BEEHIVE-953, and with the last week's release candidates, we seem
pretty stable for 1.0.
So, I'd like to propose promoting Beehive 1.0 rc4 to be released as
1.0 final.
The release candidate is here:
http://cvs.apache.org/dist/beehive/1.0-rc4/
and was built at SVN change 291405.
The vote will run until 6 PM GMT, Monday 9/28.
Adding my +1.
Eddie
Vote:
[+1] Yes, promote rc4 to Beehive 1.0 final
[0] Abstain / not sure.
[-1] No, 1.0 rc4 isn't ready to release as 1.0 final. If you vote
this way, please provide an explanation why and add what can be done
to address your concerns.
Re: [vote] promote Beehive 1.0 rc4 to Beehive 1.0
Posted by Eddie O'Neil <ek...@gmail.com>.
Apologies for the date error -- that should read "Wednesday, 9/28"
Eddie
On 9/26/05, Steve Hanson <st...@gmail.com> wrote:
> +1
>
> On 9/26/05, Daryl Olander <do...@gmail.com> wrote:
> >
> > +1....So far my testing hasn't found anything....
> >
> > On 9/26/05, Rich Feit <ri...@gmail.com> wrote:
> > >
> > > Here's my +1.
> > >
> > > Are we saying the vote is running until 6pm on *Wednesday*?
> > >
> > > Rich
> > >
> > > Eddie O'Neil wrote:
> > >
> > > > All right, let's try this again. :)
> > > >
> > > > Just uploaded installers for Beehive 1.0 rc4. It's different from
> > > >rc3 only in that it fixes the EJB control assembly problem in
> > > >BEEHIVE-953, and with the last week's release candidates, we seem
> > > >pretty stable for 1.0.
> > > >
> > > > So, I'd like to propose promoting Beehive 1.0 rc4 to be released as
> > > >1.0 final.
> > > >
> > > > The release candidate is here:
> > > >
> > > > http://cvs.apache.org/dist/beehive/1.0-rc4/
> > > >
> > > >and was built at SVN change 291405.
> > > >
> > > > The vote will run until 6 PM GMT, Monday 9/28.
> > > >
> > > > Adding my +1.
> > > >
> > > >Eddie
> > > >
> > > >
> > > > Vote:
> > > >[+1] Yes, promote rc4 to Beehive 1.0 final
> > > >[0] Abstain / not sure.
> > > >[-1] No, 1.0 rc4 isn't ready to release as 1.0 final. If you vote
> > > >this way, please provide an explanation why and add what can be done
> > > >to address your concerns.
> > > >
> > > >
> > > >
> > >
> >
> >
>
>
Re: [vote] promote Beehive 1.0 rc4 to Beehive 1.0
Posted by Steve Hanson <st...@gmail.com>.
+1
On 9/26/05, Daryl Olander <do...@gmail.com> wrote:
>
> +1....So far my testing hasn't found anything....
>
> On 9/26/05, Rich Feit <ri...@gmail.com> wrote:
> >
> > Here's my +1.
> >
> > Are we saying the vote is running until 6pm on *Wednesday*?
> >
> > Rich
> >
> > Eddie O'Neil wrote:
> >
> > > All right, let's try this again. :)
> > >
> > > Just uploaded installers for Beehive 1.0 rc4. It's different from
> > >rc3 only in that it fixes the EJB control assembly problem in
> > >BEEHIVE-953, and with the last week's release candidates, we seem
> > >pretty stable for 1.0.
> > >
> > > So, I'd like to propose promoting Beehive 1.0 rc4 to be released as
> > >1.0 final.
> > >
> > > The release candidate is here:
> > >
> > > http://cvs.apache.org/dist/beehive/1.0-rc4/
> > >
> > >and was built at SVN change 291405.
> > >
> > > The vote will run until 6 PM GMT, Monday 9/28.
> > >
> > > Adding my +1.
> > >
> > >Eddie
> > >
> > >
> > > Vote:
> > >[+1] Yes, promote rc4 to Beehive 1.0 final
> > >[0] Abstain / not sure.
> > >[-1] No, 1.0 rc4 isn't ready to release as 1.0 final. If you vote
> > >this way, please provide an explanation why and add what can be done
> > >to address your concerns.
> > >
> > >
> > >
> >
>
>
Re: [vote] promote Beehive 1.0 rc4 to Beehive 1.0
Posted by Daryl Olander <do...@gmail.com>.
+1....So far my testing hasn't found anything....
On 9/26/05, Rich Feit <ri...@gmail.com> wrote:
>
> Here's my +1.
>
> Are we saying the vote is running until 6pm on *Wednesday*?
>
> Rich
>
> Eddie O'Neil wrote:
>
> > All right, let's try this again. :)
> >
> > Just uploaded installers for Beehive 1.0 rc4. It's different from
> >rc3 only in that it fixes the EJB control assembly problem in
> >BEEHIVE-953, and with the last week's release candidates, we seem
> >pretty stable for 1.0.
> >
> > So, I'd like to propose promoting Beehive 1.0 rc4 to be released as
> >1.0 final.
> >
> > The release candidate is here:
> >
> > http://cvs.apache.org/dist/beehive/1.0-rc4/
> >
> >and was built at SVN change 291405.
> >
> > The vote will run until 6 PM GMT, Monday 9/28.
> >
> > Adding my +1.
> >
> >Eddie
> >
> >
> > Vote:
> >[+1] Yes, promote rc4 to Beehive 1.0 final
> >[0] Abstain / not sure.
> >[-1] No, 1.0 rc4 isn't ready to release as 1.0 final. If you vote
> >this way, please provide an explanation why and add what can be done
> >to address your concerns.
> >
> >
> >
>
Re: [vote] promote Beehive 1.0 rc4 to Beehive 1.0
Posted by Rich Feit <ri...@gmail.com>.
Here's my +1.
Are we saying the vote is running until 6pm on *Wednesday*?
Rich
Eddie O'Neil wrote:
> All right, let's try this again. :)
>
> Just uploaded installers for Beehive 1.0 rc4. It's different from
>rc3 only in that it fixes the EJB control assembly problem in
>BEEHIVE-953, and with the last week's release candidates, we seem
>pretty stable for 1.0.
>
> So, I'd like to propose promoting Beehive 1.0 rc4 to be released as
>1.0 final.
>
> The release candidate is here:
>
> http://cvs.apache.org/dist/beehive/1.0-rc4/
>
>and was built at SVN change 291405.
>
> The vote will run until 6 PM GMT, Monday 9/28.
>
> Adding my +1.
>
>Eddie
>
>
> Vote:
>[+1] Yes, promote rc4 to Beehive 1.0 final
>[0] Abstain / not sure.
>[-1] No, 1.0 rc4 isn't ready to release as 1.0 final. If you vote
>this way, please provide an explanation why and add what can be done
>to address your concerns.
>
>
>
[result] Re: [vote] promote Beehive 1.0 rc4 to Beehive 1.0
Posted by Eddie O'Neil <ek...@gmail.com>.
Looks like it's official -- vote results for promoting 1.0rc4 to 1.0 are:
+1: 7
0: 0
-1: 0
It will take me a bit to spin installers (might not get to it until
tomorrow); once that's done, Rich will need to sign them, but we've
got a SVN change that has made it.
Congrats to all -- we've got a 1.0 final. :)
Eddie
On 9/27/05, Bryan Che <bc...@redhat.com> wrote:
> +1
>
> Bryan
>
> Eddie O'Neil wrote:
> > All right, let's try this again. :)
> >
> > Just uploaded installers for Beehive 1.0 rc4. It's different from
> > rc3 only in that it fixes the EJB control assembly problem in
> > BEEHIVE-953, and with the last week's release candidates, we seem
> > pretty stable for 1.0.
> >
> > So, I'd like to propose promoting Beehive 1.0 rc4 to be released as
> > 1.0 final.
> >
> > The release candidate is here:
> >
> > http://cvs.apache.org/dist/beehive/1.0-rc4/
> >
> > and was built at SVN change 291405.
> >
> > The vote will run until 6 PM GMT, Monday 9/28.
> >
> > Adding my +1.
> >
> > Eddie
> >
> >
> > Vote:
> > [+1] Yes, promote rc4 to Beehive 1.0 final
> > [0] Abstain / not sure.
> > [-1] No, 1.0 rc4 isn't ready to release as 1.0 final. If you vote
> > this way, please provide an explanation why and add what can be done
> > to address your concerns.
>
Re: [vote] promote Beehive 1.0 rc4 to Beehive 1.0
Posted by Bryan Che <bc...@redhat.com>.
+1
Bryan
Eddie O'Neil wrote:
> All right, let's try this again. :)
>
> Just uploaded installers for Beehive 1.0 rc4. It's different from
> rc3 only in that it fixes the EJB control assembly problem in
> BEEHIVE-953, and with the last week's release candidates, we seem
> pretty stable for 1.0.
>
> So, I'd like to propose promoting Beehive 1.0 rc4 to be released as
> 1.0 final.
>
> The release candidate is here:
>
> http://cvs.apache.org/dist/beehive/1.0-rc4/
>
> and was built at SVN change 291405.
>
> The vote will run until 6 PM GMT, Monday 9/28.
>
> Adding my +1.
>
> Eddie
>
>
> Vote:
> [+1] Yes, promote rc4 to Beehive 1.0 final
> [0] Abstain / not sure.
> [-1] No, 1.0 rc4 isn't ready to release as 1.0 final. If you vote
> this way, please provide an explanation why and add what can be done
> to address your concerns.