From users-return-3392-apmail-qpid-users-archive=qpid.apache.org@qpid.apache.org Thu Oct 28 23:24:57 2010 Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 63797 invoked from network); 28 Oct 2010 23:24:43 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Oct 2010 23:24:43 -0000 Received: (qmail 87609 invoked by uid 500); 28 Oct 2010 23:24:36 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 87447 invoked by uid 500); 28 Oct 2010 23:24:30 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 87070 invoked by uid 99); 28 Oct 2010 23:24:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Oct 2010 23:24:20 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of shuston@riverace.com designates 216.119.133.105 as permitted sender) Received: from [216.119.133.105] (HELO riverace.com) (216.119.133.105) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Oct 2010 23:24:13 +0000 Received: from c-24-62-19-141.hsd1.ma.comcast.net ([24.62.19.141] helo=hope) by a2s43.a2hosting.com with esmtpa (Exim 4.69) (envelope-from ) id 1PBbp1-0004B7-Js for users@qpid.apache.org; Thu, 28 Oct 2010 19:23:51 -0400 From: "Steve Huston" To: Subject: RE: Stability of 0.7.946106 packages Date: Thu, 28 Oct 2010 19:23:45 -0400 Message-ID: <8AB076E36F274E5CAE5684D043C91F27@hope> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6863 Importance: Normal In-Reply-To: Thread-Index: Act25uxYEKTk+P8jTJKV7QFWvNO9BgADkXng X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2s43.a2hosting.com X-AntiAbuse: Original Domain - qpid.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - riverace.com X-Source: X-Source-Args: X-Source-Dir: Hi Chris, I'll add my 2 cents here, but I'm sure Carl will have more to add as well. > -----Original Message----- > From: Chris Sears [mailto:csears@gmail.com]=20 > Sent: Thursday, October 28, 2010 5:27 PM > To: users@qpid.apache.org > Subject: Re: Stability of 0.7.946106 packages >=20 >=20 > On Thu, Oct 28, 2010 at 4:47 PM, Carl Trieloff=20 > wrote: > > > > Red Hat snapshots or selects a svn, and provides a stable=20 > release for=20 > > MRG independent of the Qpid release process. sometimes it=20 > may be line=20 > > up, other times not. > > > > The MRG release also carries a patch set ontop of 0.7.946106 while=20 > > maintaining ABI. Thus MRG is 0.7.946106 + a patch set, so to assume=20 > > 0.7.946106 on it's own is entirely stable would be a leap. >=20 > That does help. Thanks. >=20 > So if I went with one of these 0.7.946106 packages from Red=20 > Hat or Fedora and ran into a bug, I might get an update from=20 > Red Hat or Fedora, but the Qpid response would be to fix it=20 > 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 perspective. > Whereas if I wait for 0.8 to be released, I could expect Qpid=20 > 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=20 > working out how the release process works between all the=20 > 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 -- Steve Huston, Riverace Corporation Total Lifecycle Support for Your Networked Applications http://www.riverace.com --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org