[1.41.0] Release branch open for low-risk merges
branches\release is open for low-risk merges. Use your own judgment as to what "low-risk" is, but as always stability on trunk is one of the criteria. Towards the middle of next week we will take a look at where we stand as far as the freeze for final release. We can always decide to do a second beta, too. But please do any outstanding merges as soon as you are sure they are stable, rather than waiting until the last moment. Thanks, --Beman
As we're talking about compiler warnings and such: It appears that the fix for #1414 (fixed on Trunk ~5 months ago) hasn't been merged to Release. Can it be done for 1.41? It also looks like the newly opened #3588 might be a dup of #1414. Thanks, Richard Webb -- View this message in context: http://old.nabble.com/-1.41.0--Release-branch-open-for-low-risk-merges-tp261... Sent from the Boost - Dev mailing list archive at Nabble.com.
Beman Dawes wrote:
branches\release is open for low-risk merges.
Use your own judgment as to what "low-risk" is, but as always stability on trunk is one of the criteria.
Towards the middle of next week we will take a look at where we stand as far as the freeze for final release. We can always decide to do a second beta, too. But please do any outstanding merges as soon as you are sure they are stable, rather than waiting until the last moment.
Use your own judgment as to what "low-risk" is, but as always stability on trunk is one of the criteria.
At this point, I think that you're judgement should be the determinant as to what "low risk" is. If I were you, I would lock the release branch to make sure you absolutely know about each of of these cases. But then you're not me so you can do it the way you want. The enemy of making things better is the attempt to make things perfect. Robert Ramey
Thanks,
--Beman _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Thu, Nov 5, 2009 at 12:13 PM, Robert Ramey <ramey@rrsd.com> wrote:
Beman Dawes wrote:
branches\release is open for low-risk merges.
Use your own judgment as to what "low-risk" is, but as always stability on trunk is one of the criteria.
Towards the middle of next week we will take a look at where we stand as far as the freeze for final release. We can always decide to do a second beta, too. But please do any outstanding merges as soon as you are sure they are stable, rather than waiting until the last moment.
Use your own judgment as to what "low-risk" is, but as always stability on trunk is one of the criteria.
At this point, I think that you're judgement should be the determinant as to what "low risk" is. If I were you, I would lock the release branch to make sure you absolutely know about each of of these cases. But then you're not me so you can do it the way you want.
I'm afraid that would make the process too unwieldy. For example, I'm going to be out-of-town Saturday, Sunday, and part of Monday, and wouldn't be able to respond to requests to merge. And I really would like to encourage developers to fix warnings for 1.41.0. John's report of "an 11 Mb log file from the build, with 133 THOUSAND LINES of output" worried me. --Beman
participants (3)
-
Beman Dawes -
Richard Webb -
Robert Ramey