You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Ted Ross <tr...@redhat.com> on 2015/09/08 15:23:11 UTC
[VOTE] Qpid Dispatch Router 0.5
This is the vote thread for releasing Qpid Dispatch Router 0.5 RC2 as
the final 0.5.
Please record your vote for or against on this thread.
Thanks,
-Ted
On 09/04/2015 10:30 AM, Ted Ross wrote:
> Qpid Dispatch Router 0.5 RC2 can be found here:
>
> http://people.apache.org/~tross/qpid-dispatch-0.5rc2
>
> There are two changes since RC1:
>
> - The missing sasl configuration file is now installed
> - Listener configuration was simplified:
> o The 'insecureOk' option for authenticatePeer was removed.
> authenticatePeer is now a yes/no boolean. Insecure
> authentication methods are allowed. This feature was proving to
> be confusing and frustrating to testers. We will re-add it later
> if there is a call to do so.
> o saslMechanisms is now an optional attribute. If omitted, any
> available mechanism can be used.
>
> On 08/28/2015 09:50 AM, Ted Ross wrote:
>> I've created a release candidate for Dispatch Router 0.5. The primary
>> reason for this release is to conform to the incompatible changes in the
>> Proton API. The tarball can be found here:
>>
>> http://people.apache.org/~tross/qpid-dispatch-0.5rc1
>>
>> The following improvements and bug fixes are included in this release:
>>
>> Improvements:
>>
>> DISPATCH-98 Refactor the handling of Message Annotations
>> DISPATCH-99 Allow override of the forwarding logic on a per-address
>> basis.
>> DISPATCH-101 Create a field iterator that is specific to handling
>> address fields
>> DISPATCH-110 Provide access to recent log messages via management agent.
>> DISPATCH-121 Allow pool allocation to be switched for plain allocation
>> at build time.
>> DISPATCH-123 Separate target to build documentation.
>> DISPATCH-136 qdstat -n doesn't show the local router in the list
>> DISPATCH-142 Move proton event handling from container down to server
>> DISPATCH-145 Add identifying information to the properties map of the
>> Open performative
>> DISPATCH-149 Properly handle different detach/close scenarios for links
>> DISPATCH-152 Expose SASL-related data via management
>> DISPATCH-153 Expose full set of security capabilities via configuration
>>
>> Bug Fixes:
>>
>> DISPATCH-131 Valgrind errors during the system tests are not reported
>> DISPATCH-132 Time values overflow on 32 bit systems
>> DISPATCH-133 Router Link use-after-free
>> DISPATCH-134 Driver runs at 100% CPU intermittently
>> DISPATCH-137 Dispatch Code should be updated to support newer SASL
>> calls in qpid-proton
>> DISPATCH-143 Link-routing - Various robustness problems
>> DISPATCH-146 management query sends non string values
>> DISPATCH-154 dispatch-router coredumps when connector address is
>> unresolvable
>>
>> ---------------------------------------------------------------------
>> 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
Re: [VOTE] Qpid Dispatch Router 0.5
Posted by Ted Ross <tr...@redhat.com>.
-1
Unfortunately, I need to vote down this release candidate. Due to
PROTON-989, this release crashes when run against some of the example
configurations in its own tests folder. (Hat tip to Mick Goulish for
finding this).
I will cancel this vote and release a new RC with a workaround for this bug.
-Ted
On 09/08/2015 09:23 AM, Ted Ross wrote:
> This is the vote thread for releasing Qpid Dispatch Router 0.5 RC2 as
> the final 0.5.
>
> Please record your vote for or against on this thread.
>
> Thanks,
> -Ted
>
>
> On 09/04/2015 10:30 AM, Ted Ross wrote:
>> Qpid Dispatch Router 0.5 RC2 can be found here:
>>
>> http://people.apache.org/~tross/qpid-dispatch-0.5rc2
>>
>> There are two changes since RC1:
>>
>> - The missing sasl configuration file is now installed
>> - Listener configuration was simplified:
>> o The 'insecureOk' option for authenticatePeer was removed.
>> authenticatePeer is now a yes/no boolean. Insecure
>> authentication methods are allowed. This feature was proving to
>> be confusing and frustrating to testers. We will re-add it later
>> if there is a call to do so.
>> o saslMechanisms is now an optional attribute. If omitted, any
>> available mechanism can be used.
>>
>> On 08/28/2015 09:50 AM, Ted Ross wrote:
>>> I've created a release candidate for Dispatch Router 0.5. The primary
>>> reason for this release is to conform to the incompatible changes in the
>>> Proton API. The tarball can be found here:
>>>
>>> http://people.apache.org/~tross/qpid-dispatch-0.5rc1
>>>
>>> The following improvements and bug fixes are included in this release:
>>>
>>> Improvements:
>>>
>>> DISPATCH-98 Refactor the handling of Message Annotations
>>> DISPATCH-99 Allow override of the forwarding logic on a per-address
>>> basis.
>>> DISPATCH-101 Create a field iterator that is specific to handling
>>> address fields
>>> DISPATCH-110 Provide access to recent log messages via management agent.
>>> DISPATCH-121 Allow pool allocation to be switched for plain allocation
>>> at build time.
>>> DISPATCH-123 Separate target to build documentation.
>>> DISPATCH-136 qdstat -n doesn't show the local router in the list
>>> DISPATCH-142 Move proton event handling from container down to server
>>> DISPATCH-145 Add identifying information to the properties map of the
>>> Open performative
>>> DISPATCH-149 Properly handle different detach/close scenarios for links
>>> DISPATCH-152 Expose SASL-related data via management
>>> DISPATCH-153 Expose full set of security capabilities via configuration
>>>
>>> Bug Fixes:
>>>
>>> DISPATCH-131 Valgrind errors during the system tests are not reported
>>> DISPATCH-132 Time values overflow on 32 bit systems
>>> DISPATCH-133 Router Link use-after-free
>>> DISPATCH-134 Driver runs at 100% CPU intermittently
>>> DISPATCH-137 Dispatch Code should be updated to support newer SASL
>>> calls in qpid-proton
>>> DISPATCH-143 Link-routing - Various robustness problems
>>> DISPATCH-146 management query sends non string values
>>> DISPATCH-154 dispatch-router coredumps when connector address is
>>> unresolvable
>>>
>>> ---------------------------------------------------------------------
>>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
[VOTE-CANCELED] Qpid Dispatch Router 0.5
Posted by Ted Ross <tr...@redhat.com>.
I've canceled this vote due to a blocker problem found in RC2.
-Ted
On 09/08/2015 09:23 AM, Ted Ross wrote:
> This is the vote thread for releasing Qpid Dispatch Router 0.5 RC2 as
> the final 0.5.
>
> Please record your vote for or against on this thread.
>
> Thanks,
> -Ted
>
>
> On 09/04/2015 10:30 AM, Ted Ross wrote:
>> Qpid Dispatch Router 0.5 RC2 can be found here:
>>
>> http://people.apache.org/~tross/qpid-dispatch-0.5rc2
>>
>> There are two changes since RC1:
>>
>> - The missing sasl configuration file is now installed
>> - Listener configuration was simplified:
>> o The 'insecureOk' option for authenticatePeer was removed.
>> authenticatePeer is now a yes/no boolean. Insecure
>> authentication methods are allowed. This feature was proving to
>> be confusing and frustrating to testers. We will re-add it later
>> if there is a call to do so.
>> o saslMechanisms is now an optional attribute. If omitted, any
>> available mechanism can be used.
>>
>> On 08/28/2015 09:50 AM, Ted Ross wrote:
>>> I've created a release candidate for Dispatch Router 0.5. The primary
>>> reason for this release is to conform to the incompatible changes in the
>>> Proton API. The tarball can be found here:
>>>
>>> http://people.apache.org/~tross/qpid-dispatch-0.5rc1
>>>
>>> The following improvements and bug fixes are included in this release:
>>>
>>> Improvements:
>>>
>>> DISPATCH-98 Refactor the handling of Message Annotations
>>> DISPATCH-99 Allow override of the forwarding logic on a per-address
>>> basis.
>>> DISPATCH-101 Create a field iterator that is specific to handling
>>> address fields
>>> DISPATCH-110 Provide access to recent log messages via management agent.
>>> DISPATCH-121 Allow pool allocation to be switched for plain allocation
>>> at build time.
>>> DISPATCH-123 Separate target to build documentation.
>>> DISPATCH-136 qdstat -n doesn't show the local router in the list
>>> DISPATCH-142 Move proton event handling from container down to server
>>> DISPATCH-145 Add identifying information to the properties map of the
>>> Open performative
>>> DISPATCH-149 Properly handle different detach/close scenarios for links
>>> DISPATCH-152 Expose SASL-related data via management
>>> DISPATCH-153 Expose full set of security capabilities via configuration
>>>
>>> Bug Fixes:
>>>
>>> DISPATCH-131 Valgrind errors during the system tests are not reported
>>> DISPATCH-132 Time values overflow on 32 bit systems
>>> DISPATCH-133 Router Link use-after-free
>>> DISPATCH-134 Driver runs at 100% CPU intermittently
>>> DISPATCH-137 Dispatch Code should be updated to support newer SASL
>>> calls in qpid-proton
>>> DISPATCH-143 Link-routing - Various robustness problems
>>> DISPATCH-146 management query sends non string values
>>> DISPATCH-154 dispatch-router coredumps when connector address is
>>> unresolvable
>>>
>>> ---------------------------------------------------------------------
>>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org