Please merge each commit on 1.3-rel branch by maintainer decision of each project. (D&C, security, service, ?.)
Originally, any commit on 1.3-rel should be reviewed by release function lead. However, we have a lots of time for next patch release (1.3.1), and this is not release cycle either. Let?s apply release function lead review rule on release time (with QA cycle) only. BR, Uze Choi From: ??? (Uze Choi) [mailto:[email protected]] Sent: Friday, June 02, 2017 12:30 PM To: iotivity-dev at lists.iotivity.org Subject: IoTivity Branch strategy after 1.3.0 release. Hi All, There are several commits after 1.3.0 release. Because we still have to go further for IoTivity to be OCF1.0 CTT conformable, it will be better to continue to keep the 1.3-rel branch. Please, commit to 1.3-rel branch for OCF1.0 CTT conformance, then merge into master will be done regularly. IoTivity next version with 1.3.X tag will be created on the 1.3-rel branch. Phil, Could you make a script to execute it and enabling it into server? BR, Uze Choi -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170616/63fb505d/attachment.html>
