Release schedule

[omron93]

Hello,
is there any schedule for asio releases? (for example when asio-1.11 gets stable?)
It could be very useful to have some. Or if there is some to make it more visible.

Thanks,
Marek

[acmorrow]

+1, however, there are also several open issues that would be nice to see addressed before the next stable release

[Fale]

Hi,
I'm a Fedora/RHEL/CentOS/Oracle Linux/... maintainer of Asio and I'm starting to wondering about this too, since we are deciding if Fedora 25 (and 24) will have Asio 1.10.x or 1.11 since some programs (like MongoDB) requires 1.11

[acmorrow]

@Fale - Please be aware that the vendored copy of ASIO 1.11.0 in MongoDB 3.2 has some MongoDB modifications. In particular, cherry-picks of 915d4cf and 1d19a00, as well as local modifications to build ASIO as a library (which I think you can ignore if aiming to use system ASIO), and a local fix for #73 (see mongodb/mongo@23982c4#diff-fa52cfbedd73700b47fbf74ea3cc4ca6)

[chriskohlhoff]

For 1.11.x, there are still some API changes I want to make to bring asio in to line with the C++ networking TS proposal. This might cause minor breakage for applications already using 1.11.x and/or the master branch.

[acmorrow]

@chriskohlhoff - Could you give a quick overview of what API changes are coming?

[omron93]

@chriskohlhoff Any update in this?

[zorun]

@chriskohlhoff do you have any plans for a new release?

At least 44f3ade fixes an issue on Archlinux where asio 1.10.6 does not build anymore with recent OpenSSL: https://bugs.archlinux.org/task/48620

[chriskohlhoff]

Some time in the next week I will tag a new 1.10.8 stable release, on the branch named asio-1-10-branch. This is intended to fix openssl compatibility issues up to openssl 1.1.0.

1.10.7 was tagged at the time of the Boost 1.60 release, but unfortunately I neglected to push the branch to github. This tag does address the issue shown in that Archlinux bug.

A new development release 1.11.x off master is coming soon, once I complete the last few changes to bring asio into sync with the draft networking TS. What's remaining is mainly to add string_view support, and to do an audit of asio's interface against the proposal.

[viccpp]

Any plans/thoughts for #124?

[vinniefalco]

@2underscores-vic Adding to the discussion of movable ssl::stream, in #124

[acmorrow]

Hi @chriskohlhoff -

I realize that writing the TS and getting it accepted for C++20 is more important in the big picture, but the standalone ASIO library is also in use in projects right now, and I could use some clarification on some points:

• Any update on when we can expect another 1.11 release? It has been almost two years since 1.11.0.
• Any thoughts on when the 1.11 release series could be promoted to stable? What would need to be done? Is there any way the community can help move that forward? Are there particular issues blocking it?
• Any update on the relationship between what is on master and the current state of the networking TS (which I believe is ISO/IEC JTC1 SC22 WG21 N4625)?
• I have some patches that I'd like to offer so that the vendored copy of ASIO that I'm using doesn't diverge too far from master, but there are already a couple dozen open PRs. Is this project currently 'open' to external contributions?

Please don't take this as a complaint. I think ASIO is a great library and I'm excited to see networking become part of C++, but it is currently somewhat hard to understand the roadmap for the standalone ASIO library project and how it aligns with the C++ standards process.

Thanks again for your hard work on ASIO.

[podsvirov]

Hi all! With #128 we can easy use standalone asio from CMake projects:

find_package(asio REQUIRED)
target_link_libraries(<target_name> asio::standalone)

Those who support this idea?