I think our download page should be just that ! There's a release compatibility matrix which shows which bits currently work together - so I don't think the download page is the place to try and convey this info. The python client (as the Java client) appears to be the same package on both tables.
The current download page needs changed - it could be taken to imply to a user that the java client and broker do not interop. Some info about interop could be added, to explain that the C++ broker is not backwards compatible. Marnie Some of this discussion is really about interop and backwards compatibility. D On Thu, Jan 29, 2009 at 10:29 PM, Jonathan Robie <jonathan.ro...@redhat.com>wrote: > Carl Trieloff wrote: > >> >> >>> I'd prefer not to be separating components from the same release out by >>> AMQP >>> version as I think it sends the wrong signal and is not how we actually >>> make >>> releases i.e. we released M4 not AMQP 0-10. >>> >>> >> >> that was me, to try make it really easy to know what works with what, >> based on some questions on >> the user list. Is it not clear that it is not all part of M4? ideas to >> make it better... >> > > I liked the way we had it, but I'm happy with any approach that makes it > very clear which pieces are compatible. > > I really don't want people to download incompatible bits, shrug, and move > on to some other implementation. > > Jonathan > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > >
