Hi Mitch/Jacek,
Two updates from CTT we need now, from the test result CT1.7.8.1 (only client), CT1.7.8.3 (both server & client). Could you give us the schedule first, I hope updated CTT to be released by today. Quoted from the other email. 4. CTT1.7.8.1 (Client) ? I saw this in the logs: 0.035s INFO: Prompting "Please reset DUT's ACL in order to have empty list." 2.310s DEBUG: User interaction: OK The default ACL has wildcard (i.e. ?*?) permissions to RETRIEVE the core Resources, pstat and doxm. Did you remove the ACL in this user interaction? If you didn?t, then that * access to /oic/d still exists which explains why the device actually responded when it should have sent an error response message. Jacek, can we change this test case to have the CTT install the ACE rather than expecting the test operator do it? My guess is that most of the labs won?t have the ability to easily update ACEs during certification testing. [JH] Sure! We will do that. BR, Uze Choi From: Mitch Kettrick [mailto:[email protected]] Sent: Thursday, November 24, 2016 1:27 PM To: ??? (Uze Choi); Mitch Kettrick Cc: cert_wg at openconnectivity.org; iotivity-dev at lists.iotivity.org; 'Jacek Hryszkiewicz' Subject: RE: [Request to CWG_CB] FW: [IoTivity 1.2.1 Release working Plan] RE: [dev] [Fixed] RE: IoTivity 1.2.1 Release proposal Jacek, Can you release a new version of the CTT with all known fixes tomorrow? I'll upload it so that the IoTivity team can test with it tomorrow. Thanks, Mitch Sent from my Verizon 4G LTE smartphone -------- Original message -------- From: "??? (Uze Choi)" <[email protected]> Date: 11/23/16 7:59 PM (GMT-08:00) To: Mitch Kettrick <cpm at openconnectivity.org> Cc: cert_wg at openconnectivity.org, iotivity-dev at lists.iotivity.org, 'Jacek Hryszkiewicz' <jacek.hryszkiewicz at comarch.com> Subject: [Request to CWG_CB] FW: [IoTivity 1.2.1 Release working Plan] RE: [dev] [Fixed] RE: IoTivity 1.2.1 Release proposal Hi Mitch To meet the timeline for IoTivity 1.2.1 release, we absolutely requires both side immediate co-working, Regarding CTT issue, please resolve them and release the updated CTT immediately. >From IoTivity side, I?ll do all I can, as IoTivity release function lead. Without this collaboration action, we will fail to deliver the certification ready from IoTivity and OCF perspective, I believe. BR, Uze Choi From: ??? (Uze Choi) [mailto:[email protected]] Sent: Thursday, November 24, 2016 11:42 AM To: 'iotivity-dev at lists.iotivity.org' Cc: 'cert_wg at openconnectivity.org'; 'oswg at openconnectivity.org' Subject: [IoTivity 1.2.1 Release working Plan] RE: [dev] [Fixed] RE: IoTivity 1.2.1 Release proposal Hi All, As we agreed before, IoTivity 1.2.1 is aimed for Certification compliance. We need to release that IoTivity version at least 5 day before plugfest event so that target date is 30th Nov. Today, I?ll tag the RC1 for release 1.2.1 sooner. >From today, IoTivity will be tested against CTT latest version to sync up >together. And shared in public. This QA activity will be executed by IoTivity QA function. Except the CTT compliant issue, 1.2-rel will not accept any other merge. If non-spec compliant commit merged is needed. please communicate together for the necessity. BR, Uze Choi From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? Sent: Thursday, November 17, 2016 4:41 PM To: Heldt-Sheller, Nathan; iotivity-dev at lists.iotivity.org Cc: cert_wg at openconnectivity.org; oswg at openconnectivity.org Subject: Re: [dev] [Fixed] RE: IoTivity 1.2.1 Release proposal Hi Nathan, Definitely, we need to keep update according to CTT check until release. BR, Uze Choi --------- Original Message --------- Sender : Heldt-Sheller, Nathan <nathan.heldt-sheller at intel.com> Date : 2016-11-17 16:39 (GMT+9) Title : RE: [dev] [Fixed] RE: IoTivity 1.2.1 Release proposal Hi Uze, Thank you for managing another point release for 1.2.1. May I suggest that we cannot freeze the 1.2-rel branch this time until CTT successfully passes ALL tests? This way, we know we are truly not going to have to make a 1.2.2 J We will certainly push as hard as possible to get all Security patches done by Friday and merged into 1.2-rel, but I think we must have a full successful CTT run before we freeze 1.2-rel, tag 1.2.1, and finish QA. What do you think? Thanks, Nathan From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? Sent: Wednesday, November 16, 2016 8:21 PM To: iotivity-dev at lists.iotivity.org Cc: oswg at openconnectivity.org; cert_wg at openconnectivity.org Subject: [dev] [Fixed] RE: IoTivity 1.2.1 Release proposal Hi All, Let me fix the 1.2.1 plan. Target date is End of this Month(Nov). CTT compliant issues and bugs will be accepted. Regarding, small feature required for the product can be also acceptable in this version. By timeline view, please merge all code by this week. As I mentioned before, a commit on 1.2-rel need to be accepted by release function lead, myself also. For this Patch release, some QA activity will happen specially. Originally Patch version does not have QA testing except unit test. Regarding QA Testing we can ask to QA lead.(Sungkyu. Ko) BR, Uze Choi --------- Original Message --------- Sender : ??? <uzchoi at samsung.com> S6(??)/??/IoT Lab(S/W??)/???? Date : 2016-11-14 21:03 (GMT+9) Title : [dev] IoTivity 1.2.1 Release proposal Hi IoTivity developer. After we released the 1.2.0 version, we found some CTT compliance issues. And I figured out many people want additional patch release version fixing these issues from last week OCF F2F meeting. Let me summary my release proposal as follows. . Version: 1.2.1 . mission : CTT 1.4 alignment (to development with CTT 1.4) Each Maintainer, please send items to be in the 1.2.1 release to me. if you have something beyond CTT1.4 alignment, send items also to me. Anyway, please do not merge new feature into 1.2 rel branch except the mission related patches and bug fixes. >From the next major/minor release let?s align the OCF schedule to avoid this >kind of discrepancy/gap. Any comment will be welcomed. BR, Uze Choi _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161124/9eee748c/attachment.html>
