Boost release 1.40.0 beta 1 is available from SourceForge: http://sourceforge.net/projects/boost/files/ This release contains no new libraries, but contains numerous bug fixes for existing libraries. Boost source files with types .bz2 and .gz are created with POSIX-style (\n) line endings. Source files with types .7z and .zip are created with Windows-style (\r\n) line endings. The content is otherwise identical. Be sure to download a file with the appropriate line endings for your platform. If you are new to Boost, be sure to read the Getting Started Guide. See www.boost.org There are three known issues with beta 1: * boost/detail/scoped_enum_emulation.hpp, used by Boost.Filesystem, has a name conflict (enum_t) with Unix header rpc/types.h. Fixed in trunk, but not yet merged into the release. * Boost.Python has fixes in trunk not yet merged into to the release. * Boost.Signals has has fixes in trunk not yet merged into to the release. These issues will be resolved for the final 1.40.0 release. Other than these three known issues, please report any problems with the beta on the developers or users mailing lists. Unless unexpected problems arise, the plan is to ship the final 1.40.0 release in a week to ten days. Thanks, --The Boost release team
2009/8/15 Beman Dawes <bdawes@acm.org>:
Boost release 1.40.0 beta 1 is available from SourceForge: [...] This release contains no new libraries, but contains numerous bug fixes for existing libraries.
A few questions: 1. Are there incompatible changes wrt 1.39? If not: (for the curious) what was the rationale for naming it 1.40.0 rather than 1.39.1 if it is a bugfix only release? 2. Could you please update the calendar on http://www.boost.org/development/index.html with the new expected dates? Thank you (also to the other Boost developers) for your effort invested in this outstanding product. Ingolf
Ingolf Steinbach wrote:
2009/8/15 Beman Dawes <bdawes@acm.org>:
Boost release 1.40.0 beta 1 is available from SourceForge: [...] This release contains no new libraries, but contains numerous bug fixes for existing libraries.
A few questions:
1. Are there incompatible changes wrt 1.39? If not: (for the curious) what was the rationale for naming it 1.40.0 rather than 1.39.1 if it is a bugfix only release?
All the changes can be found at http://beta.boost.org. No single person knows if they are incompatible, or if there are incompatible changes not listed there at all. It's 1.40 because every quarterly release is 1.N+1. In general, there's no ABI or API stability, so incrementing third number can be done only when doing true bugfix releases with a small number of changes, each individually examined. This release is not like this. - Volodya
Question! I've looked at http://beta.boost.org/users/news/version_1_40_0 and there is nothing about ASIO. There were some errors in it, appeared in 1.39. Were the fixes applied to 1.40?
All the changes can be found at http://beta.boost.org.
participants (4)
-
Beman Dawes -
Ingolf Steinbach -
Roman Shmelev -
Vladimir Prus