<div dir="ltr">Ben,<br><br>Thanks for the advice!<br><br>Regards,<br>Alex.<br><br><br><div class="gmail_quote">On Thu, Feb 19, 2009 at 11:57 AM, Ben Hood <span dir="ltr"><<a href="mailto:0x6e6562@gmail.com">0x6e6562@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Alex,<br>
<div class="Ih2E3d"><br>
On Thu, Feb 19, 2009 at 9:45 AM, Alex Arnon <<a href="mailto:alex.arnon@gmail.com">alex.arnon@gmail.com</a>> wrote:<br>
> We would like to request that an erlang client version that is synchronized<br>
> with the distributed server version be made available for download.<br>
<br>
</div>At some stage soon we're going to promote the Erlang client to a<br>
supported status so that it has a released version that works with a<br>
known version of the server. No ETA on that though.<br>
<div class="Ih2E3d"><br>
> Yes, we<br>
> are aware that the client is Experimental, but having to pull and build the<br>
> tip version of the server in order to have an erlang client to play around<br>
> with is a little troublesome since we are trying to keep a "stable" Rabbit<br>
> server around on our servers.<br>
<br>
</div>IMHO never use tip for any hg repo, because it is a lucky dip. Use hg<br>
up -C default instead, apart from very short periods of time, the<br>
QA'ed default branches will be in sync with each other.<br>
<div class="Ih2E3d"><br>
> At the very least, would it be possible to post the tag of the client<br>
> version which will work with the downloadable server version?<br>
<br>
</div>I think the answer to this question is the same: always use hg up -C default<br>
<font color="#888888"><br>
Ben<br>
</font></blockquote></div><br></div>