From: Bulygin, Sergey (Bulygin_at_[hidden])
Date: 2006-03-23 10:00:41
"Christopher Kohlhoff" <chris_at_[hidden]> wrote:
> The current plan is for the next version to include breaking
> interface changes arising from the review, plus some features on
> which I would like to get more feedback (such as custom memory
> allocation and dual IPv4/6 support). At that time, in addition
> to the changelog, I will publish a list of review changes that
> are yet to be made.
Congrats, Chris and all relevant community!
Is the Asio task list available somewhere to see what is likely to be changed, compared to the current 0.3.6 version?
What is the suggested roadmap for those, who wish to adopt Asio right now? Should we use 0.3.6 as is, or should we consider those "breaking interface changes" since they are going to change conceptual library design?
PS Just as a minor hint for review wizard: it's time to change Asio status in formal_review_schedule.html from "Result Pending" to "Accepted".
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk