...
Note that the official Qpid release is a source release. The entire source tree will be released. In addition the source for various individual qpid Qpid components will also be released separately.
The released source will build and have been tested under the following platforms.
- C++ Broker
- Linux
Fedora 11 (gcc 4.4, boost 1.37) - Windows XP, Vista (32 and 64 bit) (Visual Studio 2008, Boost 1.35, 1.41)
- Linux
- Java Broker
- ??
- C++ Client
- JMS Client (Java)
- Python client
- Ruby client
- WCF client (.NET)
There may also be binary packages for various platforms available for download, but they are not the primary qpid Qpid release and they are provided entirely for user convenience.
Checklist of items for the Release:
- Ensure licensing files are correct
- Release notes/Readmes
- Ensure svn revision targeted for release builds succeed (or are reported to succeed) for the necessary platforms. Including the build time tests.
- Tag candidate release
- Run build script to build and sign release artifacts
- Upload to people.apache.org
- Move to release area.
- Announce
Release Notes:
Timeline:
Please add release note items here:
- Greatly improved cluster stability and performance.
- Persistent cluster automatically restarts from clean database
- C++ broker on Windows now has a persistence module; requires Microsoft SQL Express or higher.
Jiras to be closed:
Below are all the Blocker and critical Qpid Jiras that are targeted for 0.6.
Most of these jira's look like they just need to be reviewed. I assume this means that really they just have to be closed at this stage.
...
Jira Issues |
---|
...
|
...
|
...
Priority
...
Status
...
QPID-1984
...
Poller assertion when running reliable_replication_test
...
Andrew Stitcher
...
Blocker
...
Open
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4efd7730-8eaa-4092-8f1e-5d9d275231ee"><ac:plain-text-body><![CDATA[
...
QPID-2120
...
[race condition] asynchronous delivery and message rejection can result in out of order message deilvery
...
Martin Ritchie
...
Blocker
...
Ready To Review
...
]]></ac:plain-text-body></ac:structured-macro>
...
QPID-2055
...
failed rename may leave the broker without a log4j configuration when manipulating its contents with the LoggingManagement MBean
...
Martin Ritchie
...
Critical
...
Ready To Review
...
QPID-1830
...
BytesMessage is unreadable
...
Unassigned
...
Critical
...
Open
...
QPID-2042
...
update to the management access rights may not be saved to disk, but still report success
...
Martin Ritchie
...
Critical
...
Ready To Review
...
QPID-2040
...
failed update to the PlainPasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart
...
Martin Ritchie
...
Critical
...
Ready To Review
|
Below are all other unresolved JIRAs tagged Fix for 0.6 which we should either close or move to 'Affects 0.6' and clear the fix for value.
Jira Issues | ||||
---|---|---|---|---|
|
...
QPID-2041
...
failed update to the Base64MD5PasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart
...
Martin Ritchie
...
Critical
...