Thank you Nathan and Mitch,
I know there are lots of missed part from release perspective. >From today, let me check the readiness per feature. Anyway, we cannot delay the branch out schedule at least for test start. Considering security implementation progress and weighting from OCF spec. perspective, We can allow the feature implementation push after branch out. BR, Uze Choi From: oswg at openconnectivity.org [mailto:[email protected]] On Behalf Of Mitch Kettrick Sent: Friday, March 31, 2017 10:05 AM To: 'Heldt-Sheller, Nathan'; iotivity-dev at lists.iotivity.org; oswg at openconnectivity.org; security_os_tg at openconnectivity.org Cc: '???(Uze Choi)'; '??? ?? OCF Sec' Subject: [OCF oswg] RE: Request to postpone IoTivity 1.3-rel branch date from April 7th to April 17th Hi Nathan, I don't think pushing this out one week will impact PF #12 too much. Vendors will still have one week to integrate v1.3 if they choose. I would rather have as many security CRs implemented in v1.3 than trying to rush and miss out on some key features. As Nathan said, so many of the security CRs are related to and dependent on each other. Trying to pull out one or two of the CRs that Nathan is working on will potentially make the whole thing fall apart. Putting it back together will most likely require normative spec changes that should be avoided when possible. This is not my decision but I don't think Nathan's request sounds unreasonable. Mitch From: Heldt-Sheller, Nathan [mailto:[email protected]] Sent: Thursday, March 30, 2017 4:51 PM To: iotivity-dev at lists.iotivity.org; oswg at openconnectivity.org; security_os_tg at openconnectivity.org Cc: ???(Uze Choi) (uzchoi at samsung.com); Mitch Kettrick; ??? ?? OCF Sec Subject: Request to postpone IoTivity 1.3-rel branch date from April 7th to April 17th Hello OSWG, IoTivity-dev and OSWG Security TG, As many of you know, being a volunteer project, we?ve been short-handed on developers, and struggling to find resources for several Security features. I?ve been asking for months for additional help with a few features, but being unable to find volunteers, I have picked up implementation of these myself. However just after returning from the Amsterdam F2F, I learned that one of our key development resources was moving on to another job. I?m not able to pick up this slack, since I?m already overloaded. And because of the inter-dependent nature of these features, although myself and others have tried, it has been infeasible to cut out any additional CRs from the Security Spec? to do so would be more work than just implementing what we have (not to mention significant normative CRs). The good news is that just today I?ve gotten some temporary resource commitment from inside Intel, to pick up these newly-ownerless tasks. However I think because of the time lost over the past few weeks, and spin- up required, it would greatly increase our odds of success to have another week of development time before creating the 1.3-rel branch. Moreover, at the last OSWG Security TG meeting, I believe Dongik Lee mentioned that their team would like a little more time (if possible) to implement a couple additional items they?re working on. TLDR; if there is not a hard-stop reason why we need to branch next Friday April 7th, I propose we take an additional work-week (plus the weekend for those of us who need to work through it) and create the 1.3-rel branch on Monday April 17th. Uze, I think the decision is yours ultimately, but I?m sending to the entire list to gather feedback in case there are folks counting on this April 7th date for a reason we?re not aware of. Thanks, Nathan Heldt-Sheller OSWG Security TG Chair <http://www.avg.com/email- signature?utm_medium=email&utm_source=link&utm_campaign=sig- email&utm_content=emailclient> Virus-free. <http://www.avg.com/email- signature?utm_medium=email&utm_source=link&utm_campaign=sig- email&utm_content=emailclient> www.avg.com -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170331/cc65ef53/attachment.html>
