Two activities we can think about. - From the Jenkins we need to trigger the build verification periodically for released version. (Trevor, Could you help it) - External library dependency with exact version. It should be done from 1.2.1 release [https://jira.iotivity.org/browse/IOT-1600]
BR, Uze Choi -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Thursday, November 24, 2016 2:43 AM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] 1.2.0 build failure On ter?a-feira, 22 de novembro de 2016 15:39:54 PST Nivedita Singhvi wrote: > * It does not matter if it was working when first released, if 48hrs later > is subsequently breaks with the existing code. And all subsequent > users are affected going forward, for ever, as you point out, as it is > not removed or replaced. Most projects rev their release when something > like that happens, or provide some mitigation for users. Yes, we need an update that fixes it. That's 1.2.1 and it's coming. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
