[1.51.0] Release branch closed except by permission, beta next week
Hello everyone, The release branch is now closed for all changes except by permission from one of the release managers. The beta release is planned for next Monday. Please can you write your entries for the release notes soon. As always you can edit them directly using subversion at: https://svn.boost.org/svn/boost/website/public_html/live/feed/history/ Or you can email them to me and I'll add them for you. The release notes are linked from the main page soon after the beta is released, so it would be complete by then. You can see the work in progress at: http://www.boost.org/users/history/version_1_51_0.html Finally, remember that the release notes are being compiled on the live site now, not the beta site. thanks, Daniel
Daniel James <dnljms <at> gmail.com> writes:
You can see the work in progress at:
The link to Context (new library) is broken. Is this intended for prerelease state?
On 25 July 2012 15:07, Markus Werle <numerical.simulation@web.de> wrote:
Daniel James <dnljms <at> gmail.com> writes:
You can see the work in progress at:
The link to Context (new library) is broken. Is this intended for prerelease state?
It says a few lines above that, "Note: This version is at an early stage in its release cycle. The information listed below is incomplete and some of the documentation links may not work yet". Maybe I should make that a bit more prominent. I add the documentation to the site soon after the beta release.
Daniel James-3 wrote
Or you can email them to me and I'll add them for you. The release notes are linked from the main page soon after the beta is released, so it would be complete by then. You can see the work in progress at:
Hi, please could you add the following, Thanks, Vicente * [phrase library..[@/libs/ratio/ Ratio]:] * [@http://svn.boost.org/trac/boost/ticket/7075 #7075] Workaround for error: the type of partial specialization template parameter constant "n1" depends on another template parameter. * [phrase library..[@/libs/chrono/ Chrono]:] * [@http://svn.boost.org/trac/boost/ticket/6918 #6918] Boost Chrono compilation failure on HP uX due to undefined pthread_getcpuclockid. * [@http://svn.boost.org/trac/boost/ticket/6241 #6241] boost::chrono compilation problems without std::wstring support. * [@http://svn.boost.org/trac/boost/ticket/6987 #6987] Documentation & C++11. * [@http://svn.boost.org/trac/boost/ticket/7041 #7041] time_point.hpp depends on Boost.System. * [@http://svn.boost.org/trac/boost/ticket/7042 #7042] Avoiding time_point and duration dependency on time.h and CLOCK_REALTIME. * [@http://svn.boost.org/trac/boost/ticket/7058 #7058] Make it work when BOOST_NO_EXCEPTIONS is defined. * [@http://svn.boost.org/trac/boost/ticket/7069 #7069] Misspellings in clock_string<thread_clock>. * [@http://svn.boost.org/trac/boost/ticket/7081 #7081] WinError.h capitalization in boost/detail/win/basic_types.hpp. * [phrase library..[@/libs/thread/ Thread]:] * [@http://svn.boost.org/trac/boost/ticket/4258 #4258] Linking with boost thread does not work on mingw/gcc 4.5. * [@http://svn.boost.org/trac/boost/ticket/4885 #4885] Access violation in set_tss_data at process exit due to invalid assumption about TlsAlloc. * [@http://svn.boost.org/trac/boost/ticket/6931 #6931] mutex waits forwever with Intel Compiler and /debug:parallel * [@http://svn.boost.org/trac/boost/ticket/7044 #7044] boost 1.50.0 header missing. * [@http://svn.boost.org/trac/boost/ticket/7052 #7052] Thread: BOOST_THREAD_PROVIDES_DEPRECATED_FEATURES_SINCE_V3_0_0 only masks thread::operator==, thread::operator!= forward declarations, not definitions. * [@http://svn.boost.org/trac/boost/ticket/7066 #7066] An attempt to fix current_thread_tls_key static initialization order. * [@http://svn.boost.org/trac/boost/ticket/7074 #7074] Multiply defined symbol boost::allocator_arg. * [@http://svn.boost.org/trac/boost/ticket/7078 #7078] Trivial 64-bit warning fix on Windows for thread attribute stack size * [@http://svn.boost.org/trac/boost/ticket/7089 #7089] BOOST_THREAD_WAIT_BUG limits functionality without solving anything -- View this message in context: http://boost.2283326.n4.nabble.com/1-51-0-Release-branch-closed-except-by-pe... Sent from the Boost - Dev mailing list archive at Nabble.com.
On Tue, 24 Jul 2012, Daniel James wrote:
Hello everyone,
The release branch is now closed for all changes except by permission from one of the release managers. The beta release is planned for next Monday.
Please can you write your entries for the release notes soon. As always you can edit them directly using subversion at:
https://svn.boost.org/svn/boost/website/public_html/live/feed/history/
Or you can email them to me and I'll add them for you. The release notes are linked from the main page soon after the beta is released, so it would be complete by then. You can see the work in progress at:
http://www.boost.org/users/history/version_1_51_0.html
Finally, remember that the release notes are being compiled on the live site now, not the beta site.
I forgot to put in change 79227 from the trunk, and that is making a Boost.Graph test fail on VC++ up to version 10. Would it be OK if I pushed that in at the last minute? It has been passing the tests in the trunk for a while. There is also a tiny change (order of two function arguments) in undirected_dfs that also wasn't merged and should be before the release. I do not believe that affects any tests that are in the release branch (that code's test case was missed during merging, and that isn't worth fixing for 1.51). May I please put in those two bug fixes? Thank you. -- Jeremiah Willcock
On 7/26/2012 10:21 PM, Jeremiah Willcock wrote:
I forgot to put in change 79227 from the trunk, and that is making a Boost.Graph test fail on VC++ up to version 10. Would it be OK if I pushed that in at the last minute? It has been passing the tests in the trunk for a while.
That one looks ok.
There is also a tiny change (order of two function arguments) in undirected_dfs that also wasn't merged and should be before the release. I do not believe that affects any tests that are in the release branch
You don't believe? Or, you've ran the tests locally and have verified that the change doesn't cause tests to break on the release branch?
(that code's test case was missed during merging, and that isn't worth fixing for 1.51). May I please put in those two bug fixes? Thank you.
If the tests pass for you after a merge, go ahead. -- Eric Niebler BoostPro Computing http://www.boostpro.com
participants (5)
-
Daniel James -
Eric Niebler -
Jeremiah Willcock -
Markus Werle -
Vicente Botet