On Wed, May 27, 2009 at 9:49 AM, Martin Ritchie <ritch...@apache.org> wrote:
> for the C++ client. I agree the names can be a little obtuse but I > don't think we should hold the announcement up while people go and > edit the JIRAs. It would be nice if going forward we wrote clearer It's not really a matter of clarity as much as tense of the language used. > JIRAs. I'd at least settle for completing JIRAs fields such a setting > 'Component' so this process could become automated. As there have been +1E12, this has to come from Jira, but I think there should be a little room for language edits. How about: [C++ Broker] * [QPID-1567] - Queue replication (asynchronous) between two sites * [QPID-1669] - Client connection management in the qpid-cluster CLI utility * [QPID-1673] - Dynamic Library Build on Windows (DLL) [Java Broker] * [QPID-1583] - IP White/Black lists for virtual hosts * [QPID-1648] - Enable live reconfiguration of Log4J settings for the Java broker via JMX * [QPID-1699] - Reload security section in configuration files through JMX [C++ Client] * [QPID-1673] - Dynamic Library Build on Windows (DLL) [Java Client] * [QPID-1649] - FailoverExchange support [Ruby Client] * [QPID-1602] - SASL Support [Java Management : JMX Console] * [QPID-1500] - Mac OS X Build * [QPID-1648] - Enable live reconfiguration of Log4J settings for the Java broker via JMX * [QPID-1691] - Linux x86-64 and Solaris builds [Java Management : QMan] * [QPID-1574] - QMan WS-DM Adapter (I'd like to reword QPID-1583 a bit but I've gone for as light a touch as possible) - Aidan -- Apache Qpid - Give me convenience or give me death http://qpid.apache.org --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
