Justin,

A new RC, you say?

Well, I'll just leave this little tidbit here, ya know, just in case:

https://issues.apache.org/jira/browse/QPID-4883

/backs slowly away from my keyboard....



----- Original Message -----
> From: "Justin Ross" <[email protected]>
> To: [email protected]
> Sent: Thursday, May 23, 2013 10:34:58 AM
> Subject: Re: [VOTE] Release 0.22
> 
> This vote is withdrawn.  We'll have a new RC later today.  The only
> new change will be the cmake build fix.  Once that's available, I'll
> start a new vote thread.
> 
> Justin
> 
> On Wed, May 22, 2013 at 5:14 PM, Justin Ross <[email protected]> wrote:
> > Okay, we'll fix it tomorrow.
> >
> > On May 22, 2013 4:09 PM, "Darryl L. Pierce" <[email protected]> wrote:
> >>
> >> On Wed, May 22, 2013 at 01:54:50PM -0400, Justin Ross wrote:
> >> > RC5 contains the proposed final bits for Qpid 0.22.
> >> >
> >> > If you favor making the RC5 bits into our official release, vote +1.
> >> > If you have reason to believe RC5 is not ready for release, vote -1.
> >> >
> >> > I will close this vote on Monday, 22 May.  I know that's a little
> >> > brief, but I have some vacation time coming up soon, and I'm hoping to
> >> > finish the release before I leave.
> >>
> >> The patches for 4344 were applied in reverse on this branch and, with
> >> the last cherry-pick, the bindings/CMakeLists.txt broke the CMake
> >> changes. The conditional check for Swig < 1.3.32 is still in the file
> >> and needs to be deleted to fix CMake.
> >>
> >> This is totally my fault.
> >>
> >> --
> >> Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
> >> Delivering value year after year.
> >> Red Hat ranks #1 in value among software vendors.
> >> http://www.redhat.com/promo/vendor/
> >>
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 

-- 
-K

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to