Re: [boost] What are the things that we HAVE TO fix before shipping 1.56.0?

Subject: Re: [boost] What are the things that we HAVE TO fix before shipping 1.56.0?
From: Eric Niebler (eniebler_at_[hidden])
Date: 2014-07-29 11:31:55

On 7/29/2014 8:18 AM, Eric Niebler wrote:
> On 7/29/2014 12:32 AM, Andrey Semashev wrote:
>> On Tue, Jul 29, 2014 at 1:24 AM, Marshall Clow <mclow.lists_at_[hidden]> wrote:
>>> We’re coming down to the end of the release process, so I’m taking a poll.
>>>
>>> * What bugs do you think MUST be fixed before shipping 1.56?
>>> In other words, if bug XXX is not fixed, then (in your opinion) we should not bother making a release.
>>
>> I think the issue in the nearby thread [1] needs to be fixed before
>> the release. The fix is rather simple anyway.
>>
>> [1] http://lists.boost.org/Archives/boost/2014/07/215581.php
> 
> Did you/someone file a bug? It's unlikely to get fixed otherwise.

Sorry, I see the pull request now.[*] I agree, it'd be nice to have this
fix, but I'm not anxious to hold up the release. Marshall?

Can you point me to the operator overload in Boost.Range that is causing
this problem? The longer-term fix is to be smarter there.

Eric

[*] https://github.com/boostorg/asio/pull/7