Hi Markus This is the patches/features list from the primitive service. I?ll update the detail sooner.
<https://gerrit.iotivity.org/gerrit/#/c/3817/> https://gerrit.iotivity.org/gerrit/#/c/3817/ TIZEN application crash fix for RE <https://gerrit.iotivity.org/gerrit/#/c/3809/> https://gerrit.iotivity.org/gerrit/#/c/3809/ Sample Application bug fix for RE <https://gerrit.iotivity.org/gerrit/#/c/3899/> https://gerrit.iotivity.org/gerrit/#/c/3899/ RE crash fix in Android <https://gerrit.iotivity.org/gerrit/#/c/3869/> https://gerrit.iotivity.org/gerrit/#/c/3869/ RE Client Tizen sample applications UI fix <https://gerrit.iotivity.org/gerrit/#/c/3849/> https://gerrit.iotivity.org/gerrit/#/c/3849/ Resource Container crash fix in Tizen <https://gerrit.iotivity.org/gerrit/#/c/3847/> https://gerrit.iotivity.org/gerrit/#/c/3847/ Simulator bug fix <https://gerrit.iotivity.org/gerrit/#/c/3875/> https://gerrit.iotivity.org/gerrit/#/c/3875/ Simulator value update frequency bug fix <https://gerrit.iotivity.org/gerrit/#/c/3877/> https://gerrit.iotivity.org/gerrit/#/c/3877/ Things Configuration module crash fix <https://gerrit.iotivity.org/gerrit/#/c/3891/> https://gerrit.iotivity.org/gerrit/#/c/3891/ Things manager Tizen sample application Patch will be there sooner Resource directory device respond the other device URI correctly Patch will be there sooner RE setter use POST operation instead of PUT. BR, Uze Choi From: Markus Jung [mailto:[email protected]] Sent: Tuesday, November 24, 2015 1:44 PM To: MyeongGi Jeong Subject: Re: Fwd: [dev] IoTivity 1.0.1 patch release plan proposal Hello MyeongGi, thanks for this great overview and pointing out the gerrit change numbers. @Jon, Uze, Sachin: It would be great if you can provide me a similar overview of patches/features that should go into the next release. Could I ask for one more favor. Are these issues also documented in Jira? If yes, please change the field "affects version" to 1.0.1 and link the according change in gerrit. If no, please create Jira issues that document the changes. A single issue summarizing multiple changes should be also ok, as long the links to the gerrit changes are also documented. Thank you, Best regards, Markus ------- Original Message ------- Sender : MyeongGi Jeong<myeong.jeong at samsung.com> S5/Senior Engineer/IoT Lab./Samsung Electronics Date : Nov 20, 2015 09:55 (GMT+09:00) Title : Fwd: [dev] IoTivity 1.0.1 patch release plan proposal Hi, Jon. I'd like to ask you about code review. I think, you already know, some patchsets should be applied to next release(v1.0.1) that Markus announced. So, just I give information to you which patchsets have top-priority. Please review these patchsets first to be included to v1.0.1 gerrit link description status branch https://gerrit.iotivity.org/gerrit/#/c/3747 added build option for CoAP/TCP open master https://gerrit.iotivity.org/gerrit/#/c/3797 payload/option removal for empty message open master https://gerrit.iotivity.org/gerrit/#/c/3811 filling CoAP options correctly.( Plugfest #5 issue ) open master https://gerrit.iotivity.org/gerrit/#/c/3857 fix potential defects detected by static analysis merged master https://gerrit.iotivity.org/gerrit/#/c/3879 memory management for Arduino open master https://gerrit.iotivity.org/gerrit/#/c/4013 MAC address handling open master https://gerrit.iotivity.org/gerrit/#/c/4135 add target transport option for Android open master If you have any question, please let me know.. Thanks. Best Regards, --- MyeongGi Jeong Senior Engineer, Software Architect Software R&D Center, Samsung Electronics Co., Ltd. +82-10-3328-1130 ------- Original Message ------- Sender : Markus Jung<markus.jung85 at gmail.com> Date : 2015-11-18 19:37 (GMT+09:00) Title : [dev] IoTivity 1.0.1 patch release plan proposal Hello IoTivity maintainers, I would like to propose a plan for the 1.0.1 patch release. It should take place in December. -) Patches should be prepared until Friday 4th Dec on a separate release branch (e.g., 1.0.-dev) -) Please document and track all issues that will be patched in Jira -) The second week in Dec. can be used for QA -) The patch release can get out in the mid of Dec. (around ~15th) Please let me know what you think of this plan by end of this week. Thanks, Markus -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20151125/9856d745/attachment.html>
