That is correct? -Rick
From: ??? (Uze Choi) [mailto:[email protected]] Sent: Wednesday, April 5, 2017 7:05 PM To: Bell, Richard S <richard.s.bell at intel.com>; 'Muhammad Mushfiqul Islam' <i.mushfiq at samsung.com>; Nash, George <george.nash at intel.com> Cc: iotivity-dev at lists.iotivity.org Subject: RE: [dev] 1.3-release feature code completion check To make sure, it should work with 1.3.0 version in the end. BR, Uze Choi From: Bell, Richard S [mailto:[email protected]] Sent: Wednesday, April 05, 2017 10:53 PM To: ??? (Uze Choi); 'Muhammad Mushfiqul Islam'; Nash, George Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] 1.3-release feature code completion check I understand and we will be aligned with iotivity?. I assuming that we will be testing iotivity-upnp-bridge. Thanks, -Rick From: ??? (Uze Choi) [mailto:[email protected]] Sent: Tuesday, April 4, 2017 6:48 PM To: Bell, Richard S <richard.s.bell at intel.com<mailto:richard.s.bell at intel.com>>; 'Muhammad Mushfiqul Islam' <i.mushfiq at samsung.com<mailto:i.mushfiq at samsung.com>>; Nash, George <george.nash at intel.com<mailto:george.nash at intel.com>> Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] 1.3-release feature code completion check Hi Rick, Thank you for your answer. All release components should be aligned together regardless of repo separation. I expect IoTivity QA team may not test these modules by themselves. But they need to verify whether these pass the reasonable criteria. So communication with IoTivity QA is essential as of now. Could you update the answer based on my reply? BR, Uze Choi From: Bell, Richard S [mailto:[email protected]] Sent: Wednesday, April 05, 2017 10:24 AM To: ??? (Uze Choi); Muhammad Mushfiqul Islam; Nash, George Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] 1.3-release feature code completion check Uze, Yes, I just got back this week from vacation? Generic Java Binding expected scope is merged into master? ? Yes Test is agreed with IoTivity QA lead? And progress for TC implementation from percentage view? [Rick] Generic Java Binding is complete and has been checked into master of iotivity repository for some time. There is separate build. Please see Generic Java Binding<https://wiki.iotivity.org/generic_java_binding> wiki and I attached jira ticket? Please contact George NSH on how do the testing. ? Generic Java Binding<https://wiki.iotivity.org/generic_java_binding>: (https://jira.iotivity.org/browse/IOT-1089, Bell, Richard S richard.s.bell at intel.com<mailto:richard.s.bell at intel.com>) o Generalize Java API from Android specific to general Java Platforms including J2SE. o Allows Java development on any OS (i.e. Linux, Windows, Android, IOS, and etc.) not limited to Android UPnP Bridge Updates expected scope is merged into master? any remaining fix item? Implement progress from percentage view? Test is agreed with IoTivity QA lead? And progress for TC implementation from percentage view? [Rick] UPnP Bridge is not in the iotivity repository. UPnP Bridge is in a separate repository iotivity-upnp-bridge. I attached jira ticket? ? UPnP Bridge<https://wiki.iotivity.org/iotivity_upnp_bridge> Updates (https://jira.iotivity.org/browse/IOT-1995 Rick Bell, richard.s.bell at intel.com<mailto:richard.s.bell at intel.com>): o OCF1.0 Bridge Device compatible. o Sample OCF Light. o Adopt MPM Plugin for translation engine. o Sync with UPnP Spec update (Data Model Review) Our team had tested the UPnP Bridge for IoTIvity 1.2.0. If the QA team is willing to take over testing., we can work with them. Thanks, -Rick Bell From: ??? (Uze Choi) [mailto:[email protected]] Sent: Monday, April 3, 2017 9:47 PM To: Bell, Richard S <richard.s.bell at intel.com<mailto:richard.s.bell at intel.com>> Subject: RE: [dev] 1.3-release feature code completion check Gently reminder. I expect you are very busy after come back to office. BR, Uze Choi From: ??? (Uze Choi) [mailto:[email protected]] Sent: Monday, April 03, 2017 11:14 AM To: Bell, Richard S (richard.s.bell at intel.com<mailto:richard.s.bell at intel.com>) Subject: FW: [dev] 1.3-release feature code completion check Hi Rick, Regarding Generic Java bind, and UPnP update. May I recognize all they are in the master branch? Progress as 100%. Did you discuss with QA lead how to test this feature? All TC are made? Please check it and answer to me ASAP. BR, Uze Choi From: Srikrishna Gurugubelli [mailto:[email protected]] Sent: Saturday, April 01, 2017 12:19 AM To: ??? (Uze Choi); iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] 1.3-release feature code completion check Edited inline from implementation perspective of Introspection From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Friday, March 31, 2017 1:13 AM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] 1.3-release feature code completion check Hi All feature contributor. These are new feature list beyond existing feature from 1.2.x. Let me check the progress of each item from percentage view. Please answer the progress of each item from implementation and test perspective respectively. Because there are lots of items in the release, Let me remove the feature with no responding in spite of requests. * Example to answer. Introspection ?implementation: 100%, TC is made by IoTivity QA and 70% progress. Introspection code merged into master. any remaining fix item? Implement progress from percentage view? Fixing IoT-1965 is in progress (https://gerrit.iotivity.org/gerrit/18397) (80%) Test is agreed with IoTivity QA lead? And progress for TC implementation from percentage view? Versioning code merged into master. any remaining fix item? Implement progress from percentage view? Test is agreed with IoTivity QA lead? And progress for TC implementation from percentage view? Endpoint code merged into master. any remaining fix item? Implement progress from percentage view? Test is agreed with IoTivity QA lead? And progress for TC implementation from percentage view? Security update Feature is not merged yet, already we are communicating it. Let me tracking. MPM expected scope is merged into master? any remaining fix item? Implement progress from percentage view? Test is agreed with IoTivity QA lead? And progress for TC implementation from percentage view? AllJoyn Bridge expected scope is merged into master? any remaining fix item? Implement progress from percentage view? Test is agreed with IoTivity QA lead? And progress for TC implementation from percentage view? UPnP Bridge Updates expected scope is merged into master? any remaining fix item? Implement progress from percentage view? Test is agreed with IoTivity QA lead? And progress for TC implementation from percentage view? WiFi Easy-Setup update resource model update has been merged into master branch. Test is agreed with IoTivity QA lead? And progress for TC implementation from percentage view? CoAP Native Cloud project (Resource Model Update, Web Socket) expected scope is merged into master? any remaining fix item? Implement progress from percentage view? Test is agreed with IoTivity QA lead? And progress for TC implementation from percentage view? Generic Java Binding expected scope is merged into master? Test is agreed with IoTivity QA lead? And progress for TC implementation from percentage view? BR, Uze Choi (IoTivity Release Function Lead) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170406/f9906c2b/attachment.html>
