Given that we voted to stop releasing standalone artifacts for the pure ruby client with the last release, is there any reason to keep it in the repository?
I noticed that the first thing that happened with the 0.10 release was that a user came looking for the ruby client when the artifact went missing, found the code in the 'full release' archive instead, and just used that. A highly effective removal. I have said in the past I'd prefer to use a non-trunk attic area, but the concensus was to go for deletion, although nothing has happened since that discussion. Robbie On 11 July 2011 22:13, Darryl L. Pierce <dpie...@redhat.com> wrote: > On Mon, Jul 11, 2011 at 05:07:51PM -0400, Justin Ross wrote: >> Hello. This is a reminder that I will be producing the first 0.12 >> release candidate this week, probably Wednesday evening or Thursday >> morning (my time, US east coast). >> >> I haven't seen any requests to merge to the release branch so far. >> I know of one pending fix for a windows distribution problem (the >> one Chuck mailed about). If there are others in the wings, let me >> know so I can kick off the approval process. > > If posted a fix for BZ#704271. It's a one-line fix for the pure Ruby > APIs. > > -- > 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/ > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
