On 11/7/2016 1:15 PM, Rene Rivera wrote:
On Mon, Nov 7, 2016 at 10:23 AM, Rene Rivera <grafikrobot@gmail.com> wrote:
On Mon, Nov 7, 2016 at 10:01 AM, Edward Diener <eldiener@tropicsoft.com> wrote:
If Boost decides to push back the 1.63 release by a few weeks to satisfy this single concern, then I can see trying to push through these changes for 1.63.
We don't normally push release for "unreleased" toolsets.
Given the current introduced release build failures caused by attempts to deal with this issue (see here <https://circleci.com/gh/boostorg/boost/2190>).. I am strongly against trying to rush changes for this issue into master.
I did not mean for my stupidity ( or too quick use of one of my editor's features ) to reflect on others. But I agree that tests need to cycle through 'develop' before moving changes to 'master', and my initial response above was to support that viewpoint.