Re: [boost] [release] permission to merge atomic and lockfree

Subject: Re: [boost] [release] permission to merge atomic and lockfree
From: Tim Blechmann (tim_at_[hidden])
Date: 2012-12-07 11:58:46

>> apparently boost.atomic has been abandoned. i must admit, i'm very
>> disappointed that the original author did hardly reacted neither on-list
>> nor off-list.
>>
>> furthermore, it is blocking the release of boost.lockfree, so i'm
>> volunteering to maintain this library.
> 
> I thought we'd agreed that lockfree could be initially released for
> just compilers with native support.

yes ... however we will still be in the position that boost.atomic won't
make it and i'm afraid of zillions of error reports that the library is
not working on compiler XYZ ...

>> i'd rather see helge bahmann
>> coming back and taking over responsibility for his code, but frankly, i
>> lost all hopes that this is going to happen.
>>
>> iac, i'd like to get permission from the release managers to merge both
>> atomic and lockfree to the release branch.
> 
> As far as I'm concerned, lockfree is okay for merging. Could do with
> marking up expected failures.

regarding gcc, we would *only* have expected failures, as the required
version (4.8) is neither released nor tested ...
also, some of the failures are related to a timeout on the test machines
... especially the win32 test machines seem to be an order of magnitude
slower than the linux ones ... which is a bit unfortunate, as lock-free
data structures can only reasonably be tested with long stress tests ...

> I'll get back to you about atomic. Although it needs to have the usual
> things dealt with (libs/libraries, libs/maintainers,
> libs/atomic/index.html, marking up errors).

done ... except for marking of expected failures ... i've committed some
fixes, which hopefully resolve most issues ... still waiting for the
tests to cycle ...

tim