Hello Junmo If this schedule has ever been shared I have never seen it and it is contrary to any timeline that I have presented either at the Face-to-Face in Santa Clara or in OSWG or DCTG calls since the beginning of the year.
Starting with the Android API .. As I?ve reported the Android API is on it?s own branch which has been based on the Master branch, over the course of 0.9.0 we?ve pulled changes committed into Master out to the Android API. We have never been able to rebase against the CA branch as until very recently the CA branch would not build for Android. In fact, even today after the merge we?re still not able to build Master for Android (our developers will send an output log shortly as the build limitation is in the connectivity directory). Once the have a stable Master branch that builds for Android we can integrated the Android API branch into Master this is about 13K lines of code including unit tests, samples and the Java API and JNI implementation. This process should take about a week and then we will be ready to push the code for review to the Master Branch. Depending on how long the review takes if the decision is to hold the 0.9.1 release for the Android API then testing will want to verify the resulting base and a release can be done. Alternatively you can release 0.9.1 without the Android API and it can be included in 0.9.2 the PPRTG can make a recommendation on the best course of action. The BT/BLE feature you?ve mentioned is not clear, is it intended to be the Linux capability for the OIC GATT Service Profile? If it is then there are two clarifications we need to consider. The code for the OIC GATT service profile that we shared in the DCTG some weeks ago should be code complete by the end of April and then it could be pushed for review. The implementation is not complete yet but is will be a significant amount of code and will need careful review. The second and more important point is that the Linux implementation would not be interoperable with the Android or Tizen versions that are part of Master today. The issues about the differences in the protocol specification have been documented and discussed in DCTG calls but there has been no commitment for the protocol in the Android and Tizen implementations to be modified to match the specification and implementation of the Linux capability. In summary, the dates are mentioned in schedule that appears below are not achievable, the likely dates would be: Android-API push for review April 22nd assuming the build for Android issues are fixed today or tomorrow. OIC GATT Service Profile for Linux would push for review the week of the April 27th. Availability for release would be dependent on the review process for both components. Please let me know if you have any questions. Bernie Keany Principal Engineer OIC Development Engineering Team, Open Source Technology Center. From: ??? <junmo2.yang at samsung.com<mailto:[email protected]>> Reply-To: "junmo2.yang at samsung.com<mailto:junmo2.yang at samsung.com>" <junmo2.yang at samsung.com<mailto:junmo2.yang at samsung.com>> Date: Sunday, April 12, 2015 at 11:24 PM To: "iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>" <iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>> Subject: [dev] Schedule for IoTivity v0.9.1 Release Dear IoTivity Dev. Members, I'd like to kindly remind the schedlue of Iotivity v0.9.1. If anyone has any comment or suggestion, please share it. 4/15 Release Iotivity Official Q/A Version IoTivity - Tag Name: 0.9.1-RC1 - CA merged version - Need to all Q/A issues 4/17 Complete merge of Android API 4/20 IoTivity v0.9.1_RC1 Test Report 4/21 Release IoTiviy 0.9.1-RC2 version, incldue followings - Tag Name: 0.9.1-RC2 - Andorid API - BT/BLE should be completed 4/24 Q/A Exit (Need consent between Q/A & Dev) 4/27 Web Site Open BR, - Junmo Yang ??? (Junmo Yang, Ph.D.) Principal Engineer IoT Solution Lab./Web & Convergence Team Software R&D Center, Samsung Electronics Co.,Ltd. Mobile: +82-10-7260-7032 E-mail: junmo2.yang at samsung.com<mailto:junmo2.yang at samsung.com> [cid:MKNRCZHWKC3T at namo.co.kr] -------------- next part -------------- A non-text attachment was scrubbed... Name: 201504131524681_0EB565ZP.gif Type: image/gif Size: 13168 bytes Desc: 201504131524681_0EB565ZP.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150414/1f7efe54/attachment.gif>
