Subject: Re: [boost] [1.51][Release] Short release cycle
From: Tim Blechmann (tim_at_[hidden])
Date: 2012-06-29 06:36:01
>>> The current deadline for new libraries and breaking changes is 9th
>>> July, which is less than two weeks. If you do have a new library
>>> that want to release in 1.51, you should probably let us know very
>> what's the policy for c++11-only libraries?
> I don't know. I guess the main issue is if it will be adequately
> supported by our testers.
me neither ... i guess no one knows, because i've asked this question
before without getting any reply.
>> i could make boost.lockfree
>> depend on std::atomic to avoid that it will have to wait for
>> boost.atomic forever.
> It isn't in trunk yet, so I'm not sure if you'll have enough time for
> 1.51. The deadline is very tight. You'll really have to get in and the
> tests running straight away, and you still might not have enough time
> unless it goes very smoothly (the testers aren't that frequent, I'm
well, i must admit, i'm kind of upset by the situation:
* boost.atomic seems to be dead, at least helge does not respond anymore
and the library will probably be obsolete, because once it is merged,
all compilers will support std::atomic
* there is no policy about c++11 libraries, so i cannot merge
boost.lockfree into trunk by cutting the boost.atomic dependency
* merging boost.lockfree now is too late, for the next release, as it
is not in trunk because of the reasons mentioned above. well, it is
not like it could introduce any regressions ....
... kind of awkward, since boost.lockfree has passed the review about
one year ago ... the upside is, that maybe boost will be migrated to
git, before it will be added, so i won't have to struggle with svn merges :/
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk