qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Ross <tr...@redhat.com>
Subject Qpid Dispatch Router 0.3 RC3
Date Fri, 09 Jan 2015 18:09:59 GMT
Darryl found a couple of installation and packaging problems with RC2
which have been fixed now in RC3.  Please find RC3 at the following
location:

    http://people.apache.org/~tross/qpid-dispatch-0.3rc3/

I will start a vote for RC3 as the final 0.3 release momentarily.

-Ted

On 01/08/2015 02:50 PM, Ted Ross wrote:
> A second release candidate is now available here:
> 
>     http://people.apache.org/~tross/qpid-dispatch-0.3rc2/
> 
> The following issues have been resolved since RC1.  DISPATCH-92 was
> considered a blocker since fixing it later would constitute an
> incompatible change to the configuration format on a feature introduced
> in 0.3 (the feature being log-configuration introduced with DISPATCH-16).
> 
> DISPATCH-91  Configured log levels don't work with Python-based sources
> DISPATCH-92  Make dispatch logging configuration more flexible and
>              qpid-like
> DISPATCH-93  Multiple log entries in config file prevent qdrouterd
>              from starting
> DISPATCH-95  Connector and listener identity does not show address and
>              port.
> 
> -Ted
> 
> 
> On 12/23/2014 03:27 PM, Ted Ross wrote:
>> It's been too long since the last release of Qpid Dispatch Router.  I
>> have created a release candidate for 0.3 that can be found here:
>>
>>     http://people.apache.org/~tross/qpid-dispatch-0.3rc1/
>>
>> The following features are new in 0.3:
>>
>> DISPATCH-2 	Adhere to the AMQP Management Specification for remote
>>                 management
>> DISPATCH-34 	Multi-Leg Addressing for Broker Integration
>> DISPATCH-35 	DISPATCH-34 On-demand outbound connectors
>> DISPATCH-36 	Make max-frame-size configurable per-connector/listener
>> DISPATCH-67 	Add listener configuration for allow-no-sasl
>> DISPATCH-74 	Allow changes to logging configuration of a running
>>                 router.
>>
>> The following issues have been resolved in 0.3:
>>
>> DISPATCH-1 	Use Target Address from the link if there is no To
>>                 field in a message from a producer
>> DISPATCH-12 	Exercise qdstat in the tests
>> DISPATCH-16 	Improve logging for dispatch
>> DISPATCH-19 	DISPATCH-2 Replace the non-standard GET with the
>>                 standard QUERY
>> DISPATCH-23 	DISPATCH-2 Add the now-mandatory entity attributes
>> DISPATCH-31 	Valgrind reports memory leaks due to stubbed destructors
>> DISPATCH-33 	Use session flow control to protect the router's memory
>> DISPATCH-37 	Various memory leaks
>> DISPATCH-38 	Interpret unqualified $management as _local/$management
>> DISPATCH-39 	Use studlyCaps for standard management property names
>> DISPATCH-40 	Qdrouterd segfaults while connecting to neighbour router
>> DISPATCH-41 	Port the container to Proton Engine's new event API
>> DISPATCH-46 	dispatch crash when proton gets bad socket
>> DISPATCH-49 	Hush doxygen output
>> DISPATCH-51 	address semantics don't propagate from one router to
>>                 another
>> DISPATCH-54 	Move message metadata from delivery-annotations to
>>                 message-annotations
>> DISPATCH-56 	DISPATCH-2 Implement Create/Read/Update/Delete
>>                 operations in the agent
>> DISPATCH-59 	Inconsistency on router reconnection
>> DISPATCH-61 	Inconsistent service names for the router
>> DISPATCH-63 	Daemon operation is needed for SysV-style service
>>                 execution
>> DISPATCH-65 	Packages are needed for Ubuntu Precise (12 LTS)
>> DISPATCH-66 	NULL header fields are interpreted as present
>> DISPATCH-69 	Router container should offer ANONYMOUS-RELAY capability
>> DISPATCH-72 	Sporadic core dumps in dispatch tests
>> DISPATCH-73 	Disallow inter-router listeners and connectors if role
>>                 = standalone.
>> DISPATCH-75 	Remove reference to qdstat.conf from qdstat manpage
>> DISPATCH-76 	qd_log should not evaluate its arguments if log
>>                 statement is not enabled.
>> DISPATCH-77 	Error decoding an integer message body
>> DISPATCH-78 	Driver runs at 100% CPU after an unclean disconnect
>> DISPATCH-80 	Management schema: implement annotations and entity
>>                 inheritance as per AMQP management WD 09
>> DISPATCH-81 	Remove old management code.
>> DISPATCH-82 	Poor error handling by qdmanage and qdstat tools.
>> DISPATCH-83 	Error messages are not displayed if an error occurs
>>                 when starting in deamon mode
>> DISPATCH-85 	Remove all direct printing to stdout and stderr.
>> DISPATCH-86 	Management agent should enforce format of identifiers.
>> DISPATCH-87 	Double load of libqpid-dispatch.so
>> DISPATCH-88 	Python functions invoked without the Python lock being
>>                 held causes crash
>>
>> -Ted
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message