Hi These items are remains which I know and want to clear out. Unfortunately few does not have the Jira ticket as of now.
Let me start triage meeting with vbelow information. Please add and modify if anything is required. I wish update them into Jira system with below. Security C++ OCSecuredResource crash Randeep/saurabh sharma https://jira.iotivity.org/browse/IOT-2253/ IOT-2036 Security Justworks Unit Test Fail Jongsung Security Unit Test mfgcert OTM failed Jongsung Security Sample mfgcert OTM failed(passed discovery) Jongsung Security Dos feature enabling SRK Security Dos API enabling SRK https://gerrit.iotivity.org/gerrit/#/c/19905/ Security ace2 Resource "wc" Nathan https://gerrit.iotivity.org/gerrit/#/c/19861/ Security Cleaned up all example .json Nathan https://gerrit.iotivity.org/gerrit/#/c/19923/ Security update mbedtls (patch under review) Oleksandr https://gerrit.iotivity.org/gerrit/#/c/18917/ IOT-1928 Security SSL mutex (patch under review) Dan Mihai IOT-1876 RI EndPoint info exposure fix for doxm BG.chun RI Version info get/put from client/server Ziran https://gerrit.iotivity.org/gerrit/#/c/19535/ BR, Uze Choi From: Heldt-Sheller, Nathan [mailto:[email protected]] Sent: Tuesday, May 16, 2017 2:09 PM To: uzchoi at samsung.com; iotivity-dev at lists.iotivity.org Subject: RE: [dev] [RC2 Tagged] RE: [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Thanks Uze, I am trying to keep all known security-related issues logged in JIRA and labeled ?security?. The complete list of open issues with ?security? label and P1 is here <https://jira.iotivity.org/issues/?jql=status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20Assigned%2C%20%22To%20Do%22%2C%20%22In%20Review%22)%20AND%20priority%20%3D%20P1%20AND%20fixVersion%20%3D%20%22IoTivity%201.3.0%22%20AND%20labels%20%3D%20security%20ORDER%20BY%20priority%20DESC> . If I know an issue causes CTT failure I will make sure it is marked P1. Currently there are 3 issues I know of that I believe cause CTT failures: IOT-2224 ? ?wc? + and ? types (patch under review) IOT-2258 ? Secure and Unsecure ?ep? API in OCCreateResource() (no patch yet) IOT-1896 ? Privacy for unique IDs (patch under review) There are also 3 other issues in the above list which I am not sure will cause CTT failure but which may require fix before final release: IOT-1928 ? update mbedtls (patch under review) IOT-1876 ? SSL mutex (patch under review) IOT-2036 ? Mediator sample app (still working on correct issue resolution; see JIRA) I?m not sure IOT-2036 is a release blocker; please consult with Jihun Ha or Randeep. Also I need to go through Mitch?s email response and see if there are new security issues that don?t have a JIRA yet. We should discuss the correct process for CTT results->triage->JIRA/BZ tickets->assigned owners->etc., perhaps we can discuss this process at tomorrow?s conf call 12pm PST? Thanks, Nathan From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Monday, May 15, 2017 6:13 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] [RC2 Tagged] RE: [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks RC2 has been tagged Just before. Antu, Please start the QA with RC2 tag. There are still some know issues. Please list up them with Jira ID or git Change or context at least. These need to be managed daily basis and some of them can be triaged. BR, Uze Choi From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Monday, May 15, 2017 9:01 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] [Status update 4 for RC2 tagging] RE: [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi All, Finally provisioning feature has been fixed and acl2 patch has been merged. Let me tag the RC2 soon for QA start. If you have something to be resolved additionally, please let me know. Let me have the triage meeting at Tuesday afternoon(PST) and so on. BR, Uze Choi From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Thursday, May 11, 2017 5:00 PM To: 'Heldt-Sheller, Nathan'; iotivity-dev at lists.iotivity.org Subject: [dev] [Status update 3 for RC2 tagging] RE: [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi Nathan, Patch https://gerrit.iotivity.org/gerrit/#/c/19593/ and associated fix will be the final ones for RC2 Tagging as of now. As soon as resolved, let me know. BR, Uze Choi From: ??? (Uze Choi) [mailto:[email protected]] Sent: Thursday, May 11, 2017 2:02 PM To: 'Heldt-Sheller, Nathan'; 'iotivity-dev at lists.iotivity.org' Subject: RE: [dev] [Status update 2 for RC2 tagging] RE: [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi Nathan, Unit Test build error only happened your commit. https://gerrit.iotivity.org/gerrit/#/c/19593/ More specifically, it was from 9 to 10 patch code below. static OCEntityHandlerResult HandleACLPostRequest(const OCEntityHandlerRequest *ehRequest) { : OicSecDostype_t dos; VERIFY_SUCCESS(TAG, OC_STACK_OK == GetDos(&dos), ERROR); if ((DOS_RESET == dos.state) || (DOS_RFNOP == dos.state)) { OIC_LOG_V(WARNING, TAG, "%s /acl resource is read-only in RESET and RFNOP.", __func__); ehRet = OC_EH_NOT_ACCEPTABLE; goto exit; : } I suspect, data file is not correctly updated according to your code. The Unit Test fail is due to no resource object return from discovery callback in Resource Encapsulation test case. As you comment, I suspect json dat files in the unit test need to be updated together. Could you fix the data file /iotivity/service/resource-encapsulation/unittests/oic/* BR, Uze Choi From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Thursday, May 11, 2017 12:11 PM To: 'Heldt-Sheller, Nathan'; iotivity-dev at lists.iotivity.org Subject: Re: [dev] [Status update 2 for RC2 tagging] RE: [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi Nathan, This mediator sample apps is the very correct use case for provisioning feature. Dmitry intention looks to point out the issue over the overall operation instead of simple sample fault. If possible please check why sample does not work due to this new patch. BR, Uze Choi From: Heldt-Sheller, Nathan [mailto:[email protected]] Sent: Thursday, May 11, 2017 8:24 AM To: uzchoi at samsung.com; iotivity-dev at lists.iotivity.org Subject: RE: [dev] [Status update 2 for RC2 tagging] RE: [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Thanks Uze, The unit test failures with 19593 appear to be with new unit tests that were introduced after I submitted the change (unit tests were all working when I submitted it). I also see a comment from Dmitriy that 19593 breaks one of the sample apps (see https://jira.iotivity.org/browse/IOT-2036) but I don?t know if sample apps (especially non-OCF-1.0 samples) should hold up merging OCF 1.0 features? I would not think so myself. I am okay with merging 19593 spite of these two things, especially since it appears there is a separate patch already for fixing the sample app above, and because the original unit tests all passed with my change, because 19593 implements mandatory OCF 1.0 behavior, and will be required to pass CTT. Note that the change to /acl2 (which is actually part of many patches, not just this one) may require the samples to be updated, but this isn?t something I can do by myself. I already updated the provisioningclient and sampleserver_justworks, along with all the .json and .dat files in the provisioning samples directory. In order to conform to OCF 1.0 ? as I mentioned a while ago in an email to [dev] ? sample app owners will have to update their .json and .dat files for those samples still actively being maintained/used. And, I?m happy to help there if app owner tags me in a JIRA issue or gerrit patch. As for IOT-2023, I do not think it contains any blocking issues (it?s marked P2 for that reason) and CR32 required features are already implemented. There may be some CTT tests that are not passed, but I expect many of those during bug-fix/QA cycle once CTT is run against IoTivity RC2, right? Still, I will submit a patch for the most critical parts of 2023 in the next 24 hours, in case there are other issues still holding up RC2 tagging. Thanks for your continued efforts to get RC2 done; I?m doing everything I can to resolve blocking issues, too! Nathan From: ??? (Uze Choi) [mailto:[email protected]] Sent: Wednesday, May 10, 2017 2:09 AM To: Heldt-Sheller, Nathan <nathan.heldt-sheller at intel.com>; iotivity-dev at lists.iotivity.org Subject: RE: [dev] [Status update 2 for RC2 tagging] RE: [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi Nathan, https://gerrit.iotivity.org/gerrit/#/c/19593/ has a trouble in unit test verification, However, this new code looks not affect the unit test failure. So in case of verification issue continue, let me forcedly merge. Anyway, I cannot see patch for IOT-2023:CR32 from gerrit yet. BR, Uze Choi From: Heldt-Sheller, Nathan [ <mailto:nathan.heldt-sheller at intel.com> mailto:[email protected]] Sent: Tuesday, May 09, 2017 3:34 PM To: <mailto:uzchoi at samsung.com> uzchoi at samsung.com; <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org Subject: RE: [dev] [Status update 2 for RC2 tagging] RE: [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi Uze, Three of the six issues I?m working on are ?Resolved? ? only 2179, 2023 and 1895 remain open. However at this point Jenkins issues are preventing merge for these 3 issues (and others that are not mine, but are also P1). I?ve sent email about this but I?m not sure there is anything to do about it but keep trying. I have waited more than half a day to get a Jenkins pass/fail. Worse still, I am not able to open the failure logs to determine the reason for the failure; I get ?504 Gateway timeout? message (see screenshot below). Until these issues are resolved I?m not sure we can progress. Please advise if you have any suggestions. Thanks, Nathan cid:image001.png at 01D2C9A6.0A2B2700 From: <mailto:iotivity-dev-bounces at lists.iotivity.org> iotivity-dev-bounces at lists.iotivity.org [ <mailto:iotivity-dev-bounces at lists.iotivity.org> mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Monday, May 8, 2017 1:24 AM To: <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org Subject: [dev] [Status update 2 for RC2 tagging] RE: [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi All, Still Security blocks are blocking issue for RC2 Tagging and QA start. Please resolve them ASAP. Existing Security issue. [Dongik.Lee/Sergiy] https://jira.iotivity.org/browse/IOT-2194 [Sergiy] (SSL handshake) Still issue. https://jira.iotivity.org/browse/IOT-2107 [Sergiy] https://jira.iotivity.org/browse/IOT-1876 [Sergiy] OCF1.0 Security [Nathan] https://jira.iotivity.org/browse/IOT-2179 (IOT-2121 dependent) https://jira.iotivity.org/browse/IOT-2023 reviewing? https://jira.iotivity.org/browse/IOT-1958 reviewing? https://jira.iotivity.org/browse/IOT-1895 reviewing? https://jira.iotivity.org/browse/IOT-1795 reviewing? https://jira.iotivity.org/browse/IOT-1763 reviewing? One more, Sri, new patches for introspection as below. should they merged for RC2 tag? If yes, please resolve them soon. Introspection : newly made ones, should they be merged? https://gerrit.iotivity.org/gerrit/#/c/19541/ https://gerrit.iotivity.org/gerrit/#/c/19647/ BR, Uze Choi From: Malsbary, Todd [ <mailto:todd.malsbary at intel.com> mailto:[email protected]] Sent: Saturday, May 06, 2017 2:18 AM To: <mailto:uzchoi at samsung.com> uzchoi at samsung.com; <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org Subject: RE: [dev] [Status update for RC2 tagging] RE: [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi Uze, The fix for IOT-1941 has been merged, -Todd From: <mailto:iotivity-dev-bounces at lists.iotivity.org> iotivity-dev-bounces at lists.iotivity.org [ <mailto:iotivity-dev-bounces at lists.iotivity.org> mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Tuesday, May 2, 2017 12:52 AM To: <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org Subject: [dev] [Status update for RC2 tagging] RE: [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi There are pending issue for RC2 tag as of now. Without resolving them, we cannot make the RC2 tag and QA start again. If any issue resolved please notify to me. Existing Security issue. https://jira.iotivity.org/browse/IOT-2121 (SSL handshake) [Sergiy] under the review from Dan patch https://jira.iotivity.org/browse/IOT-2107 [Chul Lee] pending https://jira.iotivity.org/browse/IOT-1876 [surabh sharma] pending OCF1.0 Security [Nathan] https://jira.iotivity.org/browse/IOT-2179 (IOT-2121 dependent) https://jira.iotivity.org/browse/IOT-2023 reviewing? https://jira.iotivity.org/browse/IOT-1958 reviewing? https://jira.iotivity.org/browse/IOT-1895 reviewing? https://jira.iotivity.org/browse/IOT-1795 reviewing? https://jira.iotivity.org/browse/IOT-1763 reviewing? Versioning https://jira.iotivity.org/browse/IOT-2120 [Ziran] under the review by Ashok. BR, Uze Choi From: <mailto:iotivity-dev-bounces at lists.iotivity.org> 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, April 28, 2017 3:41 PM To: <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org Subject: [dev] [Status for RC2 tagging] RE: [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi All. Let me share the status as follows which are currently pending issues for RC2 tagging. I wish to make a tag early next week with these resolved. Security Onboarding issue. (SSL handshake) <https://jira.iotivity.org/browse/IOT-2121> https://jira.iotivity.org/browse/IOT-2121 [Sergiy & Randeep] Versioning https://jira.iotivity.org/browse/IOT-2120 [Ziran] OCF1.0 Security [Nathan] https://jira.iotivity.org/browse/IOT-2107 https://jira.iotivity.org/browse/IOT-2023 https://jira.iotivity.org/browse/IOT-1958 https://jira.iotivity.org/browse/IOT-1957 https://jira.iotivity.org/browse/IOT-1895 https://jira.iotivity.org/browse/IOT-1795 https://jira.iotivity.org/browse/IOT-1763 MPM https://jira.iotivity.org/browse/IOT-1941 [Todd] BR, Uze Choi From: <mailto:iotivity-dev-bounces at lists.iotivity.org> iotivity-dev-bounces at lists.iotivity.org [ <mailto:iotivity-dev-bounces at lists.iotivity.org> mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Thursday, April 27, 2017 10:04 AM To: <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org Subject: [dev] [session2-Meeting minute]: [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Session2 Participants: Dave, Nathan, Mitch, Todd, Rick Uze.Choi, anyone else? Agenda: IoTivity 1.3 Feature progress for security/MPM, AJbridge, UPnP security onboarding issue(blocking) Existing feature Security provisioning break Even https://gerrit.iotivity.org/gerrit/#/c/19237/ is merged, still issue on linux machine (Windows env, it looks work) When This patch is Tested with CTT, still we have issue. So CTT will be fixed to change a property related with Read-only. 1.3.0 Security features Once provisioning is fixed in time, all features could be merged by this week. [Nathan] MPM, AJ bridge All pending patch to be merged. Open issues need to be evaluated whether they affect CTT pass or not. (e,g: optional features) : We can triage out what to be fixed next. ? Todd reply which open jira ticket should be done for 1.3.0 release UPnP bridge Sound like pending issue. ? Rick, please share the context. General 1.3.0 release Target is pass the CTT (even though this is intermediate version), Lets focus on it. Let?s mark P1 in Jira with 1.3.0 fix version, for CTT fail issue or blocking issues. (As Nathan did it on 7 Jira tickets) Todd, Nathan, Rick to notify RC2 which contain all code patch for 1.3.0 feature. BR, Uze Choi From: ??? (Uze Choi) [ <mailto:uzchoi at samsung.com> mailto:[email protected]] Sent: Wednesday, April 26, 2017 7:54 PM To: 'iotivity-dev at lists.iotivity.org' Subject: [session1-Meeting minute]: [Triage CC schedule] [dev] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi All, Let me share the meeting minute for session1 Session1 Participants: Ziran.Sun, Sergiy, Antu, Phil, Christian, Dongik, and Uze.Choi, Randeep Agenda: IoTivity 1.3 Feature progress & CTT/Test Blocking issue The remaining jira issues could not discussed how to resolve so many items. [Discovery Endpoint] There are two issue in Discovery Endpoint. But these two issues are under the certain environment, no blocking issue for whole testing. In case of multiple interfaces [Jira will be there soon from Antu] In case of TCP connection. Missing tcp port info.. [Jira will be there soon from Antu] [Versioning] Scenario with old client to new server: looks like spec issue. [Jira will be there soon from Antu, Dwarka should help it from spec view] ? Accept version API from E.H for application developer ? [Fundamental issue still there Ziran will report back] [Security - onboarding Break] Randeep, Antu and Sergiy together resolved by today. [Randeep organize] BR, Uze Choi From: ??? (Uze Choi) [ <mailto:uzchoi at samsung.com> mailto:[email protected]] Sent: Wednesday, April 26, 2017 11:04 AM To: 'iotivity-dev at lists.iotivity.org' Subject: [WebEx Info]: [Triage CC schedule] [dev] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Web Ex detail is addressed for ?Release Triage? for feature acceptance. Taget date : 1 - 4/26 morning, 11:00 ? CET (Central European Time Zone) 2 - 4/26 afternoon, 17:00 - PST IoTivity Release Triage ? 1 session - For (Asia, Europe) - Very required: Ziran.Sun, Sergiy, Antu, Jeeheok, Phil, Christian, bg.chun, Dongik, and maintainers - WebEx info Wednesday, April 26, 2017 | 2:00 am Pacific Daylight Time (GMT-07:00) Host: OCF Staff <javascript:onEdit()> Edit | <javascript:onDel()> Cancel meeting | <javascript:addToCalendar()> Add to my calendar Meeting number: 926 165 930 Meeting password: 1234 Meeting link: <https://openconnectivity.webex.com/openconnectivity/j.php?MTID=mf6059dd35477f29e25a21f9eb0f7f7d7> https://openconnectivity.webex.com/openconnectivity/j.php?MTID=mf6059dd35477f29e25a21f9eb0f7f7d7 Audio connection: +1-415-655-0002 US Toll +1-855-797-9485 US Toll free <javascript:void(0)> Global call-in numbers <https://www.webex.com/pdf/tollfree_restrictions.pdf> Show toll-free dialing restrictions Access code: 926 165 930 IoTivity Release Triage ? 2 session - For (US) - Very required: Todd, Nathan, Rick and maintainers - WebEx info Meeting number: 921 574 122 Meeting password: 1234 Meeting link: <https://openconnectivity.webex.com/openconnectivity/j.php?MTID=mefcf78b31dccb6d7b3592b833c9ebce5> https://openconnectivity.webex.com/openconnectivity/j.php?MTID=mefcf78b31dccb6d7b3592b833c9ebce5 Audio connection: +1-415-655-0002 US Toll +1-855-797-9485 US Toll free <javascript:void(0)> Global call-in numbers <https://www.webex.com/pdf/tollfree_restrictions.pdf> Show toll-free dialing restrictions Access code: 921 574 122 BR, Uze Choi From: Dwarkaprasad Dayama [ <mailto:dwarka.dayama at samsung.com> mailto:[email protected]] Sent: Tuesday, April 25, 2017 12:00 PM To: '??? (Uze Choi)'; <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org Subject: RE: [dev] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi Uze, How about having 2 calls (1 for Pacific time zone & 1 for European time zone) in this week may be Thursday and Friday to finalize the status of this release as of now? Emails may not get rapid response sometime. Regards Dwarka ---------------------------------------------------------------------------------- Software R&D Center | Software Strategy Team | Open Source Group Open Connectivity Foundation (OCF) | Iotivity | Javascript Foundation (JSF) From: <mailto:iotivity-dev-bounces at lists.iotivity.org> iotivity-dev-bounces at lists.iotivity.org [ <mailto:iotivity-dev-bounces at lists.iotivity.org> mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Tuesday, April 25, 2017 11:49 AM To: <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org Subject: Re: [dev] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi Todd, Please update the MPM and AllSeen bridge status. Everything is merged? Otherwise, what are left and when do you expect to be done. I need the timeline for prepare the testing, without it, we cannot make the plan to move forward. BR, Uze Choi From: Srikrishna Gurugubelli [ <mailto:srikguru at microsoft.com> mailto:[email protected]] Sent: Tuesday, April 25, 2017 1:37 AM To: ??? (Uze Choi); <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org Subject: RE: [dev] [For 1.3 release RC2 ] list sharing and update request for some missing blocks My change to address feedback on Introspection turned out to be complicated. I expect to submit another patch in a couple of days. Thanks, Sri From: <mailto:iotivity-dev-bounces at lists.iotivity.org> iotivity-dev-bounces at lists.iotivity.org [ <mailto:iotivity-dev-bounces at lists.iotivity.org> mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Monday, April 24, 2017 2:35 AM To: <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org Subject: [dev] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi Sri, Ziran, Todd, Nathan, and All, Please update the progress for your feature merging? Still some pending issue to bug fix. Originally, this is the planned time to make the RC2 for QA 2 cycle start, but we are not ready to do this. At least all feature should be merged in this stage, I believe. We are behind the schedule. If the issue are not cleared by this week, Let me cut out the feature from 1.3.0 release scope. BR, Uze Choi From: ??? (Uze Choi) [ <mailto:uzchoi at samsung.com> mailto:[email protected]] Sent: Monday, April 17, 2017 8:33 PM To: <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org Subject: [for 1.3 release] list sharing and update request for some missing blocks Hi All, this is update which I know Introspection, Versioning, Endpoint are having pending patches and open issues as of now. (Sri., Ziran, bg.chun please update them) Security patches are expected to be merged by this week (Nathan commented) MPM and AllJoyn Bridge still do not know the status. (Todd, please update it) CoAP Native Cloud project. (JK, please share the progress) >From the CTT testing, discovery logic looks broken, this is test blocker and >should be cleared ASAP . (Ziran/Habib, please check it) Provisioning manager is also broken due to unidentified patch. (Sergiy is fixing it now) >From Testing case, Antu, If you have any update please update table context. Please care programming document on wiki also. Feature Overall Initial code Update fix TC ready Test Executor Contributor Documentation Introspection 90% merged IOT-1965 in review Json2cbor update Done IoTivity QA Srikrishna No API Versioning 80% merged Endpoint PM issue. payload separation In progress IoTivity QA Ziran No API Endpoint 100% merged Routing issue Done IoTivity QA bg.chun No API Security update 60% In progress (Due: 4/21) - Done IoTivity QA Nathan not yet MPM 80% merged 1 Patch reviewing In progress Todd Todd Wiki exist AllJoyn Bridge 60% In progress 4 patch (iotivity.git) In progress Todd Todd not yet UPnP Bridge 80% merged needs 1.3 compat. Done Rick Rick not yet WiFi Easy-Setup update 100% merged N/A Done IoTivity QA Jihun Wiki exist CoAP Native Cloud project 100% merged - Done JK JK not yet Generic Java Binding 90% merged N/A Done IoTivity QA Rick not yet BR, Uze Choi -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170516/05a11e29/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 38418 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170516/05a11e29/attachment.png>
