| Apache Qpid > Index > Download |
Qpid implements the AMQP Specification, and as the specification has progressed Qpid is keeping up with the updates. This means that different Qpid versions support different versions of AMQP. Here is a simple guide on what use.
Here is a matrix that describes the different versions supported by each release
Y = supported
N = unsupported
IP = in progress
P = planned
| release | 0-8 | 0-9 | 0-10 | |
| java client | M3 | Y | Y | Y |
| java client | M2.1 | Y | Y | N |
| java broker | M3 | Y | Y | N |
| java broker | trunk | Y | Y | P |
| java broker | M2.1 | Y | Y | N |
| c++ client/broker | M3 | N | N | Y |
| c++ client/broker | M2.1 | N | Y | N |
| python client | M3 | Y | Y | Y |
| python client | M2.1 | Y | Y | N |
| ruby client | M3 | Y | Y | N |
| ruby client | trunk | Y | Y | P |
| C# client | M3 | Y | N | N |
| C# client | trunk | Y | N | Y |
These releases are well tested and appropriate for production use. M3 is the latest release of Qpid.
Full release: http://www.apache.org/dist/incubator/qpid/M3-incubating/![]()
If you have any questions please mail the user list user list
These releases are intended for testing and previewing new features. They have been tested and meet reasonable quality standards.
As Qpid tracks AMQP working group public work aggressively it might be worth mailing the dev list
to check the state of svn trunk and if you want to use that to understand the current compatibility matrix.
RPMs for the builds of trunk that have passed all the tests get automatically posted and are available at cruisecontrol![]()