Do we know if IoTivity community is going to support this promptly? Thanks,
Joey Morrow From: iotivity-dev-boun...@lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Morten Nielsen Sent: Monday, September 18, 2017 5:07 PM To: Mats Wichmann <m...@wichmann.us>; IoTivity Developer List <iotivity-dev@lists.iotivity.org> Subject: Re: [dev] changes in SCons upstream - 3.0 released Nice! Sounds like we can finally get support for compiling with Visual Studio 2017 too! /Morten ________________________________ From: iotivity-dev-boun...@lists.iotivity.org<mailto:iotivity-dev-boun...@lists.iotivity.org> <iotivity-dev-boun...@lists.iotivity.org<mailto:iotivity-dev-boun...@lists.iotivity.org>> on behalf of Mats Wichmann <m...@wichmann.us<mailto:m...@wichmann.us>> Sent: Monday, September 18, 2017 4:58:01 PM To: IoTivity Developer List Subject: [dev] changes in SCons upstream - 3.0 released Two things happened on the same day (one was waiting for the other, so they were definitely linked): scons 3.0 is released the entire scons infrastructure has moved to github (or is moving but hasn't quite finished - but within a couple of days it will all be done) The scons 3.0 release matters to us because - distributions released in the future will have this in their repositories. that will affect developers who habitually upgrade their cutting-edge distro (Ubuntu, Fedora, etc) or use latest-spins of Docker and such infrastructure tools when new versions come out; long-term-support type distros will not be affected. Windows, Mac, etc. should not see an impact unless you actually install (e.g. Mac using Homebrew will probably get 3.0 in not to long and if you upgrade through brew you would get new bits); similarly if you install scons through pip (python package installer) you will need to pay attention if you don't want the new version. - 3.0 supports Python 3, and there are a few side effects, some things that work now will not work in the 3.0 scons (most noticable this is print statements, and many of those have already been cleaned over the last few months) - there may well be bugfixes we're interested in, which we can't pick up without going to 3.0. - on the other hand, there could well be things we do which won't work on 3.0 because maybe we used a feature not guaranteed to be stable, or not using as documented and is impacted by a change that did not change API. There's not likely to be an immediate impact, as jenkins, QA systems, etc. will not be changed suddenly, so don't worry for the 1.3.1 release cycle. If something does come up relating to SCons 3, assign it to me. I'll try to put up a wiki page when I learn more real details, rather than trying to post stuff to email where people won't find it when they need it. --mats _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
