qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Huston" <shus...@riverace.com>
Subject RE: Stability of 0.7.946106 packages
Date Thu, 28 Oct 2010 23:23:45 GMT
Hi Chris,

I'll add my 2 cents here, but I'm sure Carl will have more to add as

> -----Original Message-----
> From: Chris Sears [mailto:csears@gmail.com] 
> Sent: Thursday, October 28, 2010 5:27 PM
> To: users@qpid.apache.org
> Subject: Re: Stability of 0.7.946106 packages
> On Thu, Oct 28, 2010 at 4:47 PM, Carl Trieloff 
> <cctrieloff@redhat.com> wrote:
> >
> > Red Hat snapshots or selects a svn, and provides a stable 
> release for 
> > MRG independent of the Qpid release process. sometimes it 
> may be line 
> > up, other times not.
> >
> > The MRG release also carries a patch set ontop of 0.7.946106 while 
> > maintaining ABI. Thus MRG is 0.7.946106 + a patch set, so to assume 
> > 0.7.946106 on it's own is entirely stable would be a leap.
> That does help. Thanks.
> So if I went with one of these 0.7.946106 packages from Red 
> Hat or Fedora and ran into a bug, I might get an update from 
> Red Hat or Fedora, but the Qpid response would be to fix it 
> in trunk, since 0.7 is a development release.

The Qpid response is correct; I'll let Carl et al respond from Red Hat's

> Whereas if I wait for 0.8 to be released, I could expect Qpid 
> to release minor updates to fix serious bugs.

No, this isn't the way it works at this point.

> Do I have that right? Sorry if this is obvious. I'm still 
> working out how the release process works between all the 
> parties involved.

The Qpid project does releases periodically (e.g. 0.6, 0.8). There's no
commitment on the project's part to release fixes any time before the
next release. Fixes do show up on the svn trunk of course, but there's
generally no 0.6.1, etc. released by the Qpid project.

Downstream vendors (such as Red Hat) can provide services under
agreements between vendor and customer to integrate fixes and deliver
them outside the normal qpid release process.

I'm looking at adding this type of service as well, and would be happy
to discuss your needs (as well as anyone else's) here or privately.


Steve Huston, Riverace Corporation
Total Lifecycle Support for Your Networked Applications

Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org

View raw message