Hi All,
Once 1.2.1 was released, all commits on 1.2-rel has been merged back to master branch. >From now on please develop the feature or merge from dev branch into the >master branch. Commit into 1.2-rel is only for the bug fix for 1.2.0 or 1.2.1 scope. However, there are still some remaining commits for unit test settling down and script clean-up, This activity has lots of dependency and not so easy to change the branch in a single time. Especially, a commit for adding feature or causing breaking the compatibility is not acceptable. If later we fix the additional release plan from 1.2-rel, we can put the commit or merge into 1.2-rel. BR, Uze Choi From: Ziran Sun [mailto:[email protected]] Sent: Tuesday, December 13, 2016 8:38 PM To: '??? (Uze Choi)'; Philippe Coval; 'ASHOKBABU CHANNA' Subject: RE: [Iotivity-maintainers] [Merge Back request] FW: IoTivity 1.2.1 Release announcement Uze, >From RI side, we only have one left https://gerrit.iotivity.org/gerrit/#/c/14863/ It?s ready to merge but the author (Greg) would prefer to do it tomorrow morning to give others a chance to review. Best regards, Ziran From: ??? (Uze Choi) [mailto:[email protected]] Sent: 12 December 2016 06:32 To: Philippe Coval; ASHOKBABU CHANNA; ziran.sun at samsung.com Subject: RE: [Iotivity-maintainers] [Merge Back request] FW: IoTivity 1.2.1 Release announcement Hi Phil, Ashok and Ziran, Please let me know when it?s done. BR, UZe Choi From: Dave Thaler [mailto:[email protected]] Sent: Sunday, December 11, 2016 3:28 AM To: ??? (Uze Choi) Subject: RE: [Iotivity-maintainers] [Merge Back request] FW: IoTivity 1.2.1 Release announcement Everything related to the platform support project is already covered. From: iotivity-maintainers-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Wednesday, December 7, 2016 8:55 PM To: iotivity-maintainers at lists.iotivity.org Cc: iotivity-dev at lists.iotivity.org Subject: Re: [Iotivity-maintainers] [Merge Back request] FW: IoTivity 1.2.1 Release announcement Hi Maintainers (Ashok, Ziran, Randeep, Jungyoungm Jihyeok, Dave, Rick, Phil) Could you confirm 1.2-rel patches are merged back into master branch? If not now, let me know the target date to be finalized. D&C project - CA Ashok Tuesday - RI Ziran Early Next week Security Project Randeep Done Service Project JungYong Done Cloud Project Jihyeok Platform Extension-Windows Dave Done -Android Rick (UPnP together) Done -Tizen Phil Done Unit Test and Script Phil Tracking BR, Uze Choi From: ??? (Uze Choi) [mailto:[email protected]] Sent: Wednesday, December 07, 2016 6:08 PM To: iotivity-maintainers at lists.iotivity Subject: RE: [Merge Back request] FW: IoTivity 1.2.1 Release announcement Let me ask the status per each sub project soon. Please check the status first. BR, Uze Choi From: ??? (Uze Choi) [mailto:[email protected]] Sent: Friday, December 02, 2016 3:48 PM To: iotivity-maintainers at lists.iotivity Subject: [Merge Back request] FW: IoTivity 1.2.1 Release announcement Hi All, Please merge back into master on 1.2-rel. It should be done correctly with maintainer responsibility, but sometime there are missing patch on master. FYI, ISG is now considering the auto merge back mechanism from release branch into master. BR, Uze Choi From: ??? (Uze Choi) [mailto:[email protected]] Sent: Friday, December 02, 2016 2:33 PM To: 'iotivity-dev at lists.iotivity.org' Subject: IoTivity 1.2.1 Release announcement Dear All, Let me announce the 1.2.1 release. We are expecting that product with IoTivity 1.2.1 can pass the OCF certification with CTT(Certification Testing Tool) v1.4 (coming soon) Tag : 1.2.1 ( <https://gerrit.iotivity.org/gerrit/#/admin/projects/iotivity> iotivity.git) Please use 1.2.0 tag for <https://gerrit.iotivity.org/gerrit/#/admin/projects/iotivity-upnp-bridge> iotivity-upnp-bridge.git Wiki : https://wiki.iotivity.org/release_note_1.2.1 There is one test case fail from following test result from IoTivity QA (see below mail) However, it was figured out that this fail is not IoTivity issue but CTT tool issue which will be updated soon. BR, Uze Choi From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? Sent: Friday, December 02, 2016 11:38 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] CTT 1.3.21 vs. IoTivity 1.2-rel branch Dear All, Here is the test result between CTT 1.3.21 and IoTivity 1.2-rel branch. - 1.2-rel latest + https://gerrit.iotivity.org/gerrit/#/c/14621/ (It's already merged) There is only 1 issue now and I think it can be resolved with next CTT ver. TC Error Log Status CT1.1.1 (Server Only ) cid:BEI0XT4NZ5JE at namo.co.kr cid:2LL5XOK0LK7C at namo.co.kr New, Collection only From: ??? (Uze Choi) [mailto:[email protected]] Sent: Thursday, December 01, 2016 3:08 PM To: 'iotivity-dev at lists.iotivity.org'; 'cert_wg at openconnectivity.org'; 'oswg at openconnectivity.org' Subject: [IoTivity 1.2.1 release Schedule notification] : [oswg] CTT 1.3.20 vs. IoTivity 1.2-rel branch Hi All, For the IoTivity 1.2.1 release, we may need one more day for testing against CTT As reported below, Iotivity has bugs in the collection logic and /d, /p resource also. IoTivity QA team will test with the latest CTT 1.3.21 and the fixed version again. If there is no issue found from IoTivity side, IoTivity will release the 1.2.1 version promptly. BR, Uze Choi -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161214/b25578e2/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7739 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161214/b25578e2/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 18558 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161214/b25578e2/attachment-0001.png>
