Le 16/11/12 13:25, Andrey Semashev a écrit :
i'm not sure about the state of atomic, as the original author hardly reacts on emails and atm, i don't have the time to adopt it ... Are you aware of the blockers that prevent Boost.Atomic from being merged to release? Perhaps there are minor problems and we could help the author to resolve them and merge Boost.Atomic ourselves. i'm not aware of any further issues with boost.atomic. most of the issues that have been raised during the review have been resolved. the only remaining thing is the fallback for shared-memory, but according to the standard, the behavior is not really defined ... and helge originally wanted to provide a version that supports shared memory to be included into boost.interprocess ... Interprocess atomics are not the blocker for Boost.Atomic, it can be added later. Aside from Boost.Test-related errors and tester issues, tests look green in trunk (although I didn't check each one of them). So unless there is something non-obvious (Helge, could you confirm
On Fri, Nov 16, 2012 at 3:39 PM, Tim Blechmann <tim@klingt.org> wrote: this?), I'd simply merge Boost.Atomic to release as it is.
I think it is up to the author to merge to release when he is ready. Releasing a library is something that could involve a lot of maintenance effort and should be done only when the author/maintainer is ready to follow-up. Best, Vicente