[rabbitmq-discuss] rabbitmq-erlang-client lagging behind server 1.8.0

[Greg Campbell]

It's my understanding that "tip" is not what you want to use - that just
refers to the most recently committed revision in *any* branch.  See
http://www.rabbitmq.com/mercurial.html for more.

I would also welcome a release of the Erlang client, as it can be a bit
onerous to keep track of the versions under the current system. Is there any
way the community can be of assistance in this effort?

On Thu, Jul 8, 2010 at 6:10 PM, Lee Kirchhoff <lee at rightscale.com> wrote:

> Hi Matthew,
>
> Thanks for the quick feedback.
>
> A week or so ago when I used the tip (I assume that is what you mean by
> head of default branch) of rabbitmq-erlang-client it failed with the 1.8.0
> server, but I tried it again today and now it worked. The problem before was
> that the rabbit_channel:start_link/6 function was missing the CollectorPid
> parameter when called from within the client.
>
> It seems risky for us to run off anything other than a tagged version of
> rabbitmq-erlang-client. Could someone tag it at a stable point?
>
> Lee
>
>
> On Thu, Jul 8, 2010 at 11:28 AM, Matthew Sackman <matthew at rabbitmq.com>wrote:
>
>> Hi Lee,
>>
>> On Thu, Jul 08, 2010 at 10:04:17AM -0700, Lee Kirchhoff wrote:
>> > The rabbitmq-erlang-client is required by a plugin we use with the
>> > rabbitmq-server. We are currently using version 1.7.2 of the server and
>> > would like to step to 1.8.0 but are blocked because
>> rabbitmq-erlang-client
>> > is lagging back at version 1.7.0 and is incompatible with 1.8.0. Is
>> there
>> > anyone working to bring rabbitmq-erlang-client forward, and if so, when
>> is
>> > it expected to be available?
>>
>> The erlang client is unreleased. Hopefully that'll change in the near
>> future. However, until then, please use the head of the default branch
>> in the rabbitmq-erlang-client repo. We try to tag the repos with version
>> numbers when things *stop* working. So eg the erlang client tagged with
>> 1.7.0 should be the *last* version that was known to work with the 1.7.0
>> broker. However, thinking about it, I can think of at least a couple of
>> changes which would have stopped the erlang client working with 1.7.2
>> and I suspect there is no version tagged with 1.7.2. In any case, I
>> would hope that if there is no 1.8.0 tagged erlang client then the
>> latest on default should work with the 1.8.0 release. If that's not the
>> case, please let us know and we'll track down and tag the correct
>> version.
>>
>> Hopefully this mess should go away once we get to be able to release the
>> erlang client, which is a priority for us in the next few months.
>>
>> Matthew
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100709/58572e54/attachment-0001.htm>