Hi Justin,
This upcoming release is targeting to align the CTT compliant. Unfortunately, IoTivity 1.2.0 is not compliant with CTT1.3 due to discrepancy on security side. >From the last OCF F2F meeting, issue was raised for this, then last week we decided to release the 1.2.1 version with CTT 1.4 update in parallel. For the next release(we can assume 1.2.2), I can assume the list as follows. https://jira.iotivity.org/browse/IOT-1488?jql=labels%20%3D%201.2.1_candidate most important feature looks bridge support regarding multi device concept. If 1.2.2 target for that mission, release will be surely meaningful. BR, Uze Choi From: oswg at openconnectivity.org [mailto:[email protected]] On Behalf Of Justin Hutchings Sent: Saturday, November 19, 2016 3:02 AM To: uzchoi at samsung.com; Heldt-Sheller, Nathan; iotivity- dev at lists.iotivity.org Cc: oswg at openconnectivity.org; cert_wg at openconnectivity.org Subject: RE: [oswg] RE: RE: [dev] [Fixed] RE: IoTivity 1.2.1 Release proposal Hi Uze, Thanks for sharing your plan here. This won?t be quite long enough for Microsoft to complete our planned 1.2.1 changes (https://jira.iotivity.org/browse/IOT-1561?filter=11200), however, we don?t want to hold Samsung up if there?s a product need to make these changes. We should just plan to follow-up with another 1.2.x release in December or January to capture any other release blocking issues. Thanks! Justin From: oswg at openconnectivity.org [mailto:[email protected]] On Behalf Of ??? Sent: Wednesday, November 16, 2016 11:41 PM To: Heldt-Sheller, Nathan <nathan.heldt-sheller at intel.com>; iotivity- dev at lists.iotivity.org Cc: oswg at openconnectivity.org; cert_wg at openconnectivity.org Subject: [oswg] RE: 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: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] 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 <http://ext.samsung.net/mail/ext/v1/external/status/update?userid=uzchoi&do= bWFpbElEPTIwMTYxMTE3MDc0MDQ2ZXBjbXMxcDM5ZDIyNTM3NWFjNmRkNTI3ZDlhZWZiNjgxNjNl ZDM0ZiZyZWNpcGllbnRBZGRyZXNzPW9zd2dAb3BlbmNvbm5lY3Rpdml0eS5vcmc_> -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161121/ea7b2658/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13402 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161121/ea7b2658/attachment.gif>
