June, I have two reviews holding me up. The first is ZigBee which is looking pretty good witch only a few issues. It should close soon. The second is the resource directory work. It was submitted for the first time for review at 4pm ET on Friday. It has some architectural issues that I am not sure that we can close before the branch. So, I am going to accept the ZigBee work as soon as the final review is complete and make the branch. We will have to talk about RD on Monday. Pat
From: ??? [mailto:[email protected]] Sent: Sunday, September 20, 2015 12:25 AM To: Lankswert, Patrick; ???; iotivity-dev at lists.iotivity.org Subject: Re: RE: [dev] IoTivity 1.0.0 release schedule Pat, George Still rc1 has not been made. Could you let us know what the ZigBee status is for 1.0.0? Daniel Tls over RA has been completed on master branch? Sent from Mobiledesk ---?? ???--- ??? : Lankswert, Patrick/patrick.lankswert at intel.com<mailto:Patrick/patrick.lankswert at intel.com> ???? : 2015/09/18 23:20 (GMT+09:00) ?? : RE: [dev] IoTivity 1.0.0 release schedule June, Thank you. As soon as reviews have been completed here, I will do as you ask. Pat From: ???(June Yong Young) [mailto:[email protected]] Sent: Friday, September 18, 2015 6:07 AM To: Lankswert, Patrick; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] IoTivity 1.0.0 release schedule Pat, George, Samsung?s high priority features now have been completed onto master. So, would you please create a release branch for IoTivity1.0.0 and make a ?1.0.0-RC1? tag when ZigBee is completed? Vijay, Daniel, TLS over RA has been completed? Regards June June Yong Young OIC Open Sourece WG Project Planning & Requirement TG Chair IoTivity Release Function Lead Samsung Electronics Co.,Ltd. Software R&D Center, IoT Solution Lab. | Web & Convergence Team Principal Engineer T: +82-31-301-6107, M: +82-10-9530-6107 E-mail :juney at samsung.com From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of ???(June Yong Young) Sent: Wednesday, September 16, 2015 2:17 AM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] IoTivity 1.0.0 release schedule Dear IoTivity members The below is IoTivitiy 1.0.0 release schedule that was shared before. Please keep in mind that we have to complete feature implementation and release RC1 by 9/25 for the 1st activitiy. 1.0.0 : ?OIC Spec 1.0 Compliant release? ? Type for Release : Major release, Feature Driven, PlugFest #4 ? Schedule (6 weeks ahead of QA completion) (cf. Original QA request is 6 weeks ahead of QA start) ? 08/28, API freeze & Programmer?s guide freeze ? 09/18, Feature complete & Review Complete and make ?1.0.0-RC1? release to QA ? 09/25, QA 1st round complete ? 09/28, Make ?1.0.0-RC2? release to QA ? 10/02, QA 2nd round complete ? 10/05, Make ?1.0.0-RC3? release to QA ? 10/09, QA 3rd round complete ? 10/12, Website Open ? 10/27~29, Plug Fest #4 And this is the final conclusion below at the last OIC OSWG F2F meeting regarding the mandatory features that have to be in 1.0.0. ? High priority features to be pushed and released ? ? Blockwise transfer in CoAP ? CoAP serialization over TCP ? TLS support for RA (Conditional ? Depends on availability by 9/18) ? Zigbee plugin June Yong Young OIC Open Sourece WG Project Planning & Requirement TG Chair IoTivity Release Function Lead Samsung Electronics Co.,Ltd. Software R&D Center, IoT Solution Lab. | Web & Convergence Team Principal Engineer T: +82-31-301-6107, M: +82-10-9530-6107 E-mail :juney at samsung.com [http://www.samsung.net/pt_images/C10/securityimage/MSI_20140516060336843.gif] [http://ext.samsung.net/mailcheck/SeenTimeChecker?do=36652d682e3669a8d1ac7ee707c0123924c085cdfd80c7ea4312eb38dc64eeca320e382f20fd0ff68ce45660844802fa09060032c89b30e00407d1a278fe738d3298a32fe7c0f484cf878f9a26ce15a0] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150920/5905cbfb/attachment.html>
