Hi Uze, inline. -Todd On Thu, 2017-04-27 at 10:03 +0900, ??? (Uze Choi) wrote: > 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. All pending ones mentioned earlier are now merged with exception of -?https://gerrit.iotivity.org/gerrit/#/c/17621/?- I don't believe this is necessary for 1.3 -?https://gerrit.iotivity.org/gerrit/#/c/19129/?- Looks good, just waiting on +1 from you.
> ?????????? 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 I added comments to JIRA with recommended priority and fix version/s for all open tickets mentioned earlier with one exception -?https://jira.iotivity.org/browse/IOT-1941?- I have an open question about the specified behavior of this; I will update when I have an answer. > 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]? > 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]? > 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 | Cancel meeting | Add to my calendar > Meeting number: 926 165 930 > Meeting password: 1234 > Meeting link: https://openconnectivity.webex.com/openconnectivity/j.p > hp?MTID=mf6059dd35477f29e25a21f9eb0f7f7d7 > Audio connection: > +1-415-655-0002 US Toll > +1-855-797-9485 US Toll free > Global call-in numbers > 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.p > hp?MTID=mefcf78b31dccb6d7b3592b833c9ebce5 > Audio connection: > +1-415-655-0002 US Toll > +1-855-797-9485 US Toll free > Global call-in numbers > Show toll-free dialing restrictions > Access code: 921 574 122 > ? > BR, Uze Choi > From: Dwarkaprasad Dayama [mailto:dwarka.dayama at samsung.com]? > Sent: Tuesday, April 25, 2017 12:00 PM > To: '??? (Uze Choi)'; 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-bo > unces at lists.iotivity.org] On Behalf Of ??? (Uze Choi) > Sent: Tuesday, April 25, 2017 11:49 AM > To: 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]? > Sent: Tuesday, April 25, 2017 1:37 AM > To: ??? (Uze Choi); 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-bo > unces at lists.iotivity.org] On Behalf Of ??? (Uze Choi) > Sent: Monday, April 24, 2017 2:35 AM > To: 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]? > Sent: Monday, April 17, 2017 8:33 PM > To: 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 T > C ready Test Executor Contributor Documentation > Introspection???? 90% merged IOT-1965 in > reviewJson2cbor update Done IoTivity QA Srikrish > na 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 - D > one JK JK not yet > Generic Java Binding?????? 90% merged N/A > Done IoTivity QA Rick not yet > ? > BR, Uze Choi > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
