Currently, the CI infrastructure provisions three generations of Visual Studio: 2013, 2015, 2017. Jenkins builds happen against the 2013 and 2015 versions in both 32-bit and 64-bit mode, which contribute to the "verified" vote; 2017 exists but is not used. Is there a transition plan to enable 2017 and phase out 2013 (which feels like it would not be as useful any longer - of course Microsoft's official public recommendation is to use VS2017)? If there isn't, should we make such a plan?
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
