This issue tracks the release note for the following Fedora Change:
Fedora 28 Boost 1.66 upgrade owned by @jwakely
If you own this change, please add additional information here that we should communicate to Fedora users. Specifically, please consider:
Your notes to us do not need to be formally written. We will edit them and add details as needed. This is a way for you to ensure that we know what is critical about your change.
If you want to write this release note, then:
Once you're done with the above, make sure to either commit the relnote to an appropriate section of the Release Notes book, or, if you're not familiar with Git, AsciiDoc, or whatever else, just add it to this issue as a comment and let pbokoc[1] and Brian ( @bex ) know that you're done with this one and you'd like the note included. Also make sure to do this even for relnotes that haven't been checked by the change owner.
[0] You can do that by asking the change owner listed on the wiki page; alternatively you can infer it by checking the tracker bug (linked in Wiki) in Bugzilla and looking at its status; see bug comments for details. Ask someone on the mailing list or on IRC if you're not sure. [1] In #fedora-docs on FreeNode (UTC+1 timezone, online mostly during the day on weekdays), or pbokoc @redhat.com if you can't get a hold of me on IRC.
Boost has been upgraded to version 1.66. Apart from a number of bugfixes and improvements to existing libraries, this brings several new libraries compared to Fedora 27: Boost.PolyCollection, Boost.Stacktrace, Boost.Beast, Boost.CallableTraits, Boost.Mp11.
One library has been removed, Boost.TR1, and a number of deprecated APIs in Boost.Asio have been removed. Code using Boost.TR1 should be modified to use the equivalent features provided by other Bosot libraries (e.g. Boost.Tuple, Boost.Unordered) or in the C++ standard library (e.g. std::tuple, std::unordered_map). Code using the deprecated Asio APIs should be modified by removing the io_service arguments.
std::tuple
std::unordered_map
io_service
Metadata Update from @pbokoc: - Issue assigned to pbokoc
Fixed in PR #168
Metadata Update from @pbokoc: - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.