I too was on the call, added my name to notes below. From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? (Uze Choi) Sent: Wednesday, April 26, 2017 6:04 PM To: 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, Omar, 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/<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgerrit.iotivity.org%2Fgerrit%2F%23%2Fc%2F19237%2F&data=02%7C01%7Comarm%40microsoft.com%7Cab034c5e47704fa6b35c08d48d0969e1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636288518972778086&sdata=rybuKmAHXRaKZ6rwmAPz4EhVvyDUkVKzYYMaav5ExHE%3D&reserved=0> 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:[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:[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 Edit <javascript:onEdit()> | Cancel meeting<javascript:onDel()> | Add to my calendar<javascript:addToCalendar()> Meeting number: 926 165 930 Meeting password: 1234 Meeting link: https://openconnectivity.webex.com/openconnectivity/j.php?MTID=mf6059dd35477f29e25a21f9eb0f7f7d7<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenconnectivity.webex.com%2Fopenconnectivity%2Fj.php%3FMTID%3Dmf6059dd35477f29e25a21f9eb0f7f7d7&data=02%7C01%7Comarm%40microsoft.com%7Cab034c5e47704fa6b35c08d48d0969e1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636288518972778086&sdata=8GtOOt7Lrx8oaEoJbjv9qLM4bOCjjDnVNl5%2FqXKx4jM%3D&reserved=0> Audio connection: +1-415-655-0002 US Toll +1-855-797-9485 US Toll free Global call-in numbers<javascript:void(0)> Show toll-free dialing restrictions<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.webex.com%2Fpdf%2Ftollfree_restrictions.pdf&data=02%7C01%7Comarm%40microsoft.com%7Cab034c5e47704fa6b35c08d48d0969e1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636288518972778086&sdata=YmddLFOLKPMf0eOGNJU4MNZUayD2LO6zRsqHRCd0zKU%3D&reserved=0> 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenconnectivity.webex.com%2Fopenconnectivity%2Fj.php%3FMTID%3Dmefcf78b31dccb6d7b3592b833c9ebce5&data=02%7C01%7Comarm%40microsoft.com%7Cab034c5e47704fa6b35c08d48d0969e1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636288518972778086&sdata=IbJapJK9%2FA%2BDpQokenAsNKwvWvO8VGW%2BVJoE%2FRbizXA%3D&reserved=0> Audio connection: +1-415-655-0002 US Toll +1-855-797-9485 US Toll free Global call-in numbers<javascript:void(0)> Show toll-free dialing restrictions<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.webex.com%2Fpdf%2Ftollfree_restrictions.pdf&data=02%7C01%7Comarm%40microsoft.com%7Cab034c5e47704fa6b35c08d48d0969e1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636288518972778086&sdata=YmddLFOLKPMf0eOGNJU4MNZUayD2LO6zRsqHRCd0zKU%3D&reserved=0> Access code: 921 574 122 BR, Uze Choi From: Dwarkaprasad Dayama [mailto:[email protected]] Sent: Tuesday, April 25, 2017 12:00 PM To: '??? (Uze Choi)'; iotivity-dev at lists.iotivity.org<mailto: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: 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: iotivity-dev at lists.iotivity.org<mailto: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:[email protected]] Sent: Tuesday, April 25, 2017 1:37 AM To: ??? (Uze Choi); iotivity-dev at lists.iotivity.org<mailto: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: 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: iotivity-dev at lists.iotivity.org<mailto: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:[email protected]] Sent: Monday, April 17, 2017 8:33 PM To: iotivity-dev at lists.iotivity.org<mailto: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)
