Uze, Wednesday - 4/26 5:00PM PST works for me. Thanks, -Rick
-----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Malsbary, Todd Sent: Tuesday, April 25, 2017 9:11 AM To: iotivity-dev at lists.iotivity.org; uzchoi at samsung.com Subject: Re: [dev] [Triage CC schedule] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi Uze, Sounds good, thanks for doing this. ?17:00 PST 4/26 works for me. -Todd On Tue, 2017-04-25 at 13:40 +0900, ??? (Uze Choi) wrote: > I see. Good proposal, > ? > Let me create the two calls 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 > ? > 1 session (Asia, Europe) > Very required: Ziran.Sun, Sergiy, Antu, Jeeheok, Phil, Christian, > bg.chun, Dongik, and maintainers > ? > 2 session (US) > Very required: Todd, Nathan, Rick and maintainers > ? > Let me send the webex connection info tomorrow. > ? > 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 _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
