The recent VS2015 toolchain switch led to us shipping broken binaries to canary users for 3.5 days. While early testing against the VS2015 toolchain occurred, one build configuration was missed which caused breaking code generation changes. Having a documented process in place should minimize the likelihood of this occurring in the future. It will also preserve the institutional knowledge which is at risk of rotting due to the relative rarity of this task.
The recent VS2015 toolchain switch led to us shipping broken binaries to canary users for 3.5 days. While early testing against the VS2015 toolchain occurred, one build configuration was missed which caused breaking code generation changes. Having a documented process in place should minimize the likelihood of this occurring in the future. It will also preserve the institutional knowledge which is at risk of rotting due to the relative rarity of this task.