Re: [boost] [msm] [release] 1.68.0 post-beta merges

Subject: Re: [boost] [msm] [release] 1.68.0 post-beta merges
From: Deniz Bahadir (dbahadir_at_[hidden])
Date: 2018-08-01 14:23:15

Am 13.07.2018 um 08:16 schrieb Deniz Bahadir via Boost:
> Am 12.07.2018 um 22:26 schrieb Marshall Clow via Boost:
>> On Wed, Jul 11, 2018 at 3:14 AM, Deniz Bahadir via Boost <
>> boost_at_[hidden]> wrote:
>>
>>> Hi guys,
>>> Hi Christophe,
>>>
>>> Am 11.07.2018 um 01:10 schrieb Marshall Clow via Boost:
>>>
>>>> The master branch is is now open for post-beta merges, but only as
>>>> described in the Post-Beta Merge Policy. See
>>>> <https://github.com/boostorg/boost/wiki/Release-Beta-Merge-Policy>
>>>>
>>>>
>>> Would it be possible to include the simple fix for Boost.MSM from
>>> pull-request #15 (https://github.com/boostorg/msm/pull/15)?
>>>
>>> That one fixes compilation of Boost.MSM with C++17.
>>> std::random_shuffle was removed from the standard-library and therefore
>>> needs to be conditionally handled in Boost.MSM. (That problem occurs 
>>> with
>>> libc++ 6 for example.)
>>>
>>
>> Has it been tested on develop? Are the tests passing?
> 
> I cannot tell. It is still a pull-request and not merged in the develop 
> branch of Boost.MSM. Is there some way I can explicitly trigger testing 
> that pull-request? (The automatically started Travis-tests all passed.)
> 

As I did not see any further reaction, neither on Github or via e-Mail, 
I assume this pull-request will not make it int the next Boost release!? 
So Boost.MSM needs local modifications if used in C++17 environment...

> Note, that I am not the author/maintainer of Boost.MSM. I am just the 
> one providing the pull-request and asking for it being included.
> 

Is Christophe still active on Boost and still maintaining Boost.MSM? Or 
is anyone else maintaining it?

>> If so, yes.
> 
> That would be great.
> 

Deniz