On 16/12/2017 00:47, John Maddock wrote:
I was expecting the updates to config to be included in 1.66.0.
How? Our release process was started before 15.5 was released, and the configuration changes are not especially trivial - and we're still without a volunteer running the regression tests for 15.5 so while I'm reasonably sure they don't break the libraries that depend on those macros since I tested before and after changes against develop, I confess I'm less sure what happens when we integrate everything to master.
This does not seem like the first time a new MSVC release occurred just days prior to a Boost release, causing consternation amongst people who expected the latter to work with the former. Perhaps the release schedules are too similar, and Boost should apply a permanent calendar offset to give more time to react? Or perhaps people should react more pro-actively to the preview releases (a common theme I've heard posted here is to ignore preview releases because things will be different in the final release)?