Please work on the 1.3-rel branch rather than master. Merging to mater will be done regularly.
Final perfect code could be in the master, but testable code should be merged in 1.3-rel branch I think. After this week passed, no more time to test the iotivity code for release I think, even though we have another time to test but this will not be for newly introduced code but regression test. In shortly, I wish you finalize your module in 1.3-rel even with some limitation/incompleteness. Of course, This will not be acceptable to master. BR, Uze Choi -----Original Message----- From: Malsbary, Todd [mailto:[email protected]] Sent: Wednesday, April 26, 2017 1:08 AM To: iotivity-dev at lists.iotivity.org; uzchoi at samsung.com Subject: Re: [dev] [For 1.3 release RC2 ] list sharing and update request for some missing blocks Hi Uze, Sorry for the delay. Here's the current status: MPM Would like to cherry pick these to 1.3-rel. A couple have build issues so not ready yet. - https://gerrit.iotivity.org/gerrit/#/c/19165/ - https://gerrit.iotivity.org/gerrit/#/c/19167/ - https://gerrit.iotivity.org/gerrit/#/c/19169/ Pending, but needs fixes before getting merged - https://gerrit.iotivity.org/gerrit/#/c/17621/ Open issues - https://jira.iotivity.org/browse/IOT-2087 - https://jira.iotivity.org/browse/IOT-2094 - https://jira.iotivity.org/browse/IOT-2095 iotivity-alljoyn-bridge - 1.3-rel branch exists, need to verify with iotivity.git + patches suggested by Antu - Open tasks - Review introspection implementation and track upcoming changes - Implement oic.r.alljoynobject collection resource - Integrate with MPM Dependent open issues in iotivity.git - https://jira.iotivity.org/browse/IOT-1935 - https://jira.iotivity.org/browse/IOT-1940 - https://jira.iotivity.org/browse/IOT-1941 General spec alignment issues - https://jira.iotivity.org/browse/IOT-204 8 - https://jira.iotivity.org/browse/IOT-2056 -Todd On Tue, 2017-04-25 at 11:48 +0900, ??? (Uze Choi) wrote: > 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
