chriskohlhoff / asio

Asio C++ Library
http://think-async.com/Asio
4.98k stars 1.22k forks source link

Release schedule #84

Open omron93 opened 9 years ago

omron93 commented 9 years ago

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 commented 9 years ago

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

Fale commented 8 years ago

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 commented 8 years ago

@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 915d4cf6f0b105249ab788839420b857c5d2fe03 and 1d19a0060146cc345787158ab564f77e02a03568, 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 https://github.com/chriskohlhoff/asio/issues/73 (see https://github.com/mongodb/mongo/commit/23982c4d0b11b445c54f0ec4ad58edbd837fe7e4#diff-fa52cfbedd73700b47fbf74ea3cc4ca6)

chriskohlhoff commented 8 years ago

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 commented 8 years ago

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

omron93 commented 8 years ago

@chriskohlhoff Any update in this?

zorun commented 8 years ago

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

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

chriskohlhoff commented 8 years ago

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 commented 8 years ago

Any plans/thoughts for #124?

vinniefalco commented 8 years ago

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

acmorrow commented 7 years ago

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:

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 commented 7 years ago

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?

acmorrow commented 7 years ago

@chriskohlhoff - We have been very excited and happy to see renewed activity on the master branch of ASIO.

Several of the recent changes have proven very valuable for some PoC work we are doing to evaluate techniques for decoupling network processing from database processing in MongoDB. However, we do need to start planning for our next stable release. It would be very helpful for us if we had some idea of what the roadmap looked like for seeing the recent work on master (and for that matter, the work in 1.10.0...1.11.0 too) land in a new stable release, so that we can make an informed decision about whether or not we can depend on these new features or not.

Any insight you can share would be greatly appreciated. Thanks!