[1.46.1] branches/release open for bug fixes only
We are going to do a point release next week. branches/release is now open for merging bug fixes only, including documentation fixes. As always, please make sure the fix is stable on trunk before merging to release. The cutoff for merging is noon Eastern US time on Tuesday, March 8th. We have to hold to a tight schedule because of other commitments later in the month. --Beman
Beman Dawes wrote:
We are going to do a point release next week. branches/release is now open for merging bug fixes only, including documentation fixes.
As always, please make sure the fix is stable on trunk before merging to release.
The cutoff for merging is noon Eastern US time on Tuesday, March 8th. We have to hold to a tight schedule because of other commitments later in the month.
I want the fix for the following ticket (regression, I think) included in 1.46.1. "#4717: Non-const local static variable stored_vtable" https://svn.boost.org/trac/boost/ticket/4717 Here is a quote of a essential part of the fix. - static vtable_type stored_vtable = + static const vtable_type stored_vtable = { { &manager_type::manage }, &invoker_type::invoke }; https://svn.boost.org/trac/boost/attachment/ticket/4717/djw_function_const_v... Is it possible to include the fix, which is still not in trunk, in 1.46.1? Is there anything I can do to push the fix? (for 1.46.1 if possible, otherwise for any future releases) -- k_satoda
On 2-3-2011 2:12, Beman Dawes wrote:
We are going to do a point release next week. branches/release is now open for merging bug fixes only, including documentation fixes.
As always, please make sure the fix is stable on trunk before merging to release.
The cutoff for merging is noon Eastern US time on Tuesday, March 8th. We have to hold to a tight schedule because of other commitments later in the month.
So the branch is closed for a while for normal changes. Does this influence the deadline for new libraries for merge with Release branche? To be honest, a week delay, or somewhat more, would be convenient... Regards, Barend
On 3/3/2011 1:16 AM, Barend Gehrels wrote:
On 2-3-2011 2:12, Beman Dawes wrote:
We are going to do a point release next week. branches/release is now open for merging bug fixes only, including documentation fixes.
As always, please make sure the fix is stable on trunk before merging to release.
The cutoff for merging is noon Eastern US time on Tuesday, March 8th. We have to hold to a tight schedule because of other commitments later in the month.
So the branch is closed for a while for normal changes.
Does this influence the deadline for new libraries for merge with Release branche?
Thanks for checking. Please don't merge new libraries to release until 1.46.1 is done and Beman gives the all-clear. -- Eric Niebler BoostPro Computing http://www.boostpro.com
Would it also be possible to merge the fix for warning in boost/thread/pthread/condition_variable.hpp for 1.46.1 that is already in trunk? https://svn.boost.org/trac/boost/ticket/4818 It was fixed 8 weeks ago and I believe it was supposed to be merged but never made it to release for 1.46.0. I still see the problem under gcc 4.4 under OpenSuSE 11.1. The warning pops up all over the place, so it is particularly distracting. Cheers! Andrew Hundt On Wed, Mar 2, 2011 at 8:39 PM, Eric Niebler <eric@boostpro.com> wrote:
On 3/3/2011 1:16 AM, Barend Gehrels wrote:
On 2-3-2011 2:12, Beman Dawes wrote:
We are going to do a point release next week. branches/release is now open for merging bug fixes only, including documentation fixes.
As always, please make sure the fix is stable on trunk before merging to release.
The cutoff for merging is noon Eastern US time on Tuesday, March 8th. We have to hold to a tight schedule because of other commitments later in the month.
So the branch is closed for a while for normal changes.
Does this influence the deadline for new libraries for merge with Release branche?
Thanks for checking. Please don't merge new libraries to release until 1.46.1 is done and Beman gives the all-clear.
-- Eric Niebler BoostPro Computing http://www.boostpro.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On 3/3/2011 9:52 AM, Andrew Hundt wrote:
Would it also be possible to merge the fix for warning in boost/thread/pthread/condition_variable.hpp for 1.46.1 that is already in trunk? https://svn.boost.org/trac/boost/ticket/4818
It was fixed 8 weeks ago and I believe it was supposed to be merged but never made it to release for 1.46.0. I still see the problem under gcc 4.4 under OpenSuSE 11.1. The warning pops up all over the place, so it is particularly distracting.
I suggest you bring this to the attention of the Boost.Thread maintainer. Thanks, -- Eric Niebler BoostPro Computing http://www.boostpro.com
On 3/1/2011 5:12 PM, Beman Dawes wrote:
We are going to do a point release next week. branches/release is now open for merging bug fixes only, including documentation fixes.
As always, please make sure the fix is stable on trunk before merging to release.
The cutoff for merging is noon Eastern US time on Tuesday, March 8th. We have to hold to a tight schedule because of other commitments later in the month.
I just entered a documentation ticket #5258 (apologies if I didn't get the correct components and version settings...). It looks like there was at least one important fix for the Iostreams library that occurred in V1.46. The fix was for ticket #4590 However, there is no end user documentation (release notes) that this fix occurred. It would be nice if a note could be added to the library release notes for this release. To help out I added a proposed patch to the above ticket which contains a change for the iostreams library release notes documentation (I hope this looks okay). Ideally it would be nice if a note could be added to the relevant "http://www.boost.org/users/download/version_1_46_0" what's new page for iostreams too. I would have added a quick patch for this too, but I don't know where this lives in the source tree (the contents of above patch is probably all that needs to be added).
participants (6)
-
Andrew Hundt -
Barend Gehrels -
Beman Dawes -
eg -
Eric Niebler -
Kazutoshi Satoda