0.10 Release
Status
- 4 April: RC3 released
- 1 April: Release delayed to the week of 4 April
- 24 March: RC2 released
- 17 March: RC1 released
- 3 March: Release branch created
- 22 February: Alpha released
Links
Feature and improvement jiras |
|
Open bug jiras |
|
Open unassigned bug jiras |
|
Candidate bug jiras |
|
Fixed bug jiras |
|
Release branch |
http://svn.apache.org/repos/asf/qpid/branches/0.10/ |
Alpha distribution |
|
Beta distribution |
|
RC1 distribution |
|
RC2 distribution |
|
RC3 distribution |
Schedule
16 February
- Alpha
- Trunk remains open
- Feature integration ends
- The alpha release tests the release process after the introduction of major features
2 March, 2 weeks later
- Beta
- Branch for release (trunk remains open)
- Release branch commits require approval
- Release manager produces outstanding bug report, triages bugs
16 March, 2 weeks later
- RC1
23 March, 1 week later
- RC2
30 March, 1 week later
- RC3
- Targeted release date
Changes requiring user attention
- The C++ broker now enables producer flow control by default.
Features and improvements
- QPID-529: The C++ broker now supports priority-ordered message queuing.
- QPID-1916: The Java release now includes Maven artifacts for the Java client.
- QPID-2104: The C++ broker has an improved last-value queue implementation.
- QPID-2921: In the C++ broker, message completion is now an asynchronous operation in more situations.
- QPID-2934: C++ QMF agents can now authorize incoming method calls using an authentication ID passed with the corresponding message.
- QPID-2958: The .NET binding to the C++ client now targets an older version of the .NET Framework, 2.0, for broader compatibility.
- QPID-2966: The C++ broker now allows administrators to alter logging levels at runtime.
- QPID-3000: The C++ broker now optionally waits a configured time before removing auto-delete queues.
- QPID-3002: The C++ broker now generates alerts when queues reach a certain depth.
- QPID-3015: The C++ broker now supports creating queues and exchanges via QMF.
- QPID-3031: The C++ client now allows setting the SSL certificate name in the connection options.
- QPID-3032: You can now use more fine-grained ACLs to control QMF operations on the C++ broker.
- QPID-3067: Examples using the old messaging API have been isolated under a common directory.
- QPID-3115: Some cases where the C++ and python clients' connection options differed have been reconciled.