On Mon, 2 May 2011, Robbie Gemmell wrote:

On 2 May 2011 18:01, Rajith Attapattu <[email protected]> wrote:


 http://qpid.apache.org/release_notes_0.10.html

Justin, the above link does not seem to contain the following sections.
"Changes requiring user attention"
"Known issues"

Is this deliberate or was this an oversight ?
I would prefer if we can include the above in our release notes as well.


My bad, I simply put together a similar page to the one I did previously to
consolidate the JIRA issues. I have applied Justin's patch to update it.

Thank you, Robbie.

I have one more thing to ask. I sampled some previous announcements, and they're all from @apache.org mail addresses. I don't have one of those to send from, and I want to avoid any faux pas. Would you post the release announcement to [email protected]?

Justin

---

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid 0.10.

Apache Qpid (http://qpid.apache.org) is a cross-platform enterprise messaging solution which implements the Advanced Message Queuing Protocol (AMQP, http://www.amqp.org). It provides brokers written in C++ and Java, along with clients for C++, Java JMS, .Net, Python, and Ruby.

Qpid 0.10 is available from our website:

  http://qpid.apache.org/download.cgi

The 0.10 release has undergone a lot of bug fixing and feature enhancement. We recommend that all users upgrade. A few changes of note:

  - The C++ broker now supports priority-ordered message queueing
  - The C++ broker and client now implement producer flow control
  - The Java JMS client is now available via Maven

A comprehensive list of features, improvements, and bugs resolved in the 0.10 release is available here:

  http://qpid.apache.org/release_notes_0.10.html

Thanks to all the users and contributors who have helped to improve Apache Qpid.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to