On 7 Nov 2016, at 18:15, Rene Rivera
wrote: On Mon, Nov 7, 2016 at 10:23 AM, Rene Rivera
wrote: On Mon, Nov 7, 2016 at 10:01 AM, Edward Diener
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.
Possibly so, but I don't think you can call MSVS 2015 Update 3 an "unreleased" toolset. It is the current latest production version. You might be thinking of MSVS "15" - the successor to 2015 that /is/ still in beta. And yes you wouldn't be the first to remark on the awkward name! Pete