Dear All,
It looks a lot of confusion there, so I would like to say what we have been doing so far. To be clear, the release management function activity has been made so far officially like below. If anything looks problem, please let me know, then I?ll consider it. - Release Schedule, the list of the features, feature complete to be decided and announced by Release Management Function Lead - Creating branch, tagging to be done by Pat or Uze right now (case by case) by a request from release management function due to time difference. Sometimes, the specific feature can be done first in US, sometimes it can be done first in Korea. This has been officially asked by release management function. - Release Management Function member is assigned for each member compnany. So, Release Management Funtion role is being done through the communication among persons below. . Korea : June myself . Intel : Pat was delegated from George at present (when will it be replanced?) . MediaTek: Felix June Yong Young OIC Open Sourece WG Project Planning & Requirement TG Chair IoTivity Release Function Lead Samsung Electronics Co.,Ltd. Software R&D Center, IoT Solution Lab. | Web & Convergence Team Principal Engineer T: +82-31-301-6107, M: +82-10-9530-6107 E-mail :juney at samsung.com From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of JinGuk Jeong Sent: Tuesday, July 21, 2015 10:17 AM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] 0.9.2-dev Branch created, feature FREEZE for Plugfest 3 Pat, Yes, I think release branch management is a task in release management. June, In my opinion, this task is your task. Is that right? It is the best that you will do it by yourselves. If you want to delegate some tasks or ask for someguys' help, I think you need to do it officially. BR Jinguk Jeong ------- Original Message ------- Sender : Lankswert, Patrick<patrick.lankswert at intel.com> Date : 2015-07-20 23:56 (GMT+09:00) Title : RE: [dev] 0.9.2-dev Branch created, feature FREEZE for Plugfest 3 Jinguk, Ok, so, to be clear, you are asking us to provide the information to June so that he can announce this. This raises another issue though. You are right, Erich, Jon and I are just discovery and connectivity. We have been doing the release branches, GIT management and maintenance. Should these also be done in release management? Pat From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? Sent: Monday, July 20, 2015 10:32 AM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] 0.9.2-dev Branch created, feature FREEZE for Plugfest 3 Pat, I know that June announced target date. However you and Erich can just know the status of discovery & connectivity project in detail. By the way, it seems that Erich's email was about whole IoTivity projects. I think each role has each responsibility. So, In my opinion, it is better that release management function leader do a his role. BR Jinguk Jeong ---?? ???--- ??? : Lankswert, Patrick/patrick.lankswert at intel.com ???? : 2015/07/20 22:42 (GMT+09:00) ?? : RE: [dev] 0.9.2-dev Branch created, feature FREEZE for Plugfest 3 Jinguk, The feature freeze was announce last week. The process announced before even that. Erich is just reporting that the work was done. If you want Erich and I to report it to June, so that he can announce the completion of the work, we can do that but it seems like an unnecessary delay. Pat From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? Sent: Sunday, July 19, 2015 10:54 PM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] 0.9.2-dev Branch created, feature FREEZE for Plugfest 3 Feature-freeze for release version can be announced by release management function leader. I'm little confused why this email was sent by sub-maintainer. BR Jinguk Jeong ------- Original Message ------- Sender : Keane, Erich<erich.keane at intel.com> Date : 2015-07-18 10:04 (GMT+09:00) Title : [dev] 0.9.2-dev Branch created, feature FREEZE for Plugfest 3 Hi all- As you know, today is the feature-freeze for the Plugfest 3. I've created a branch to contain this version, which will receive bug-fixes as they are discovered. Additionally, the tag 0.9.2-beta has been created to be used as a reference for validation. The major features of this release are: CBOR, Experimental IPv6 Support, Experimental Remote-Access Support. Currently, The Android server is having trouble PUT/POST requests. Additionally, the LOW QOS observation cancellation does not properly work throughout the stack, resulting in the server continuing to send out notifications. For the RI/CA layers, please continue to submit fixes to all bugs to master (noting that they apply to the 0.9.2-dev branch), and I will cherry-pick them to the branch. If your patch applies ONLY to the 0.9.2-dev branch you'll be required to explain to Pat why that is the case, and we'll discuss it from there. General feature-development can still be contributed to master, though they will not be included in the Plugfest 3 release. Validation: Feel free to test the 0.9.2-dev branch or the 0.9.2-beta tag, though note that the former will be changing with bug-fixes. I anticipate a number of bug fixes and a -rc1 sometime next week. Thank you all for your contributions, and have a great weekend! -Erich _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Jinguk Jeong, Software R&D Center, SAMSUNG ELECTRONICS CO., LTD Email : jinguk.jeong at samsung.com 010-3244-4110 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Jinguk Jeong, Software R&D Center, SAMSUNG ELECTRONICS CO., LTD Email : jinguk.jeong at samsung.com 010-3244-4110 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ <http://ext.samsung.net/mailcheck/SeenTimeChecker?do=0fa18573320d6211b94e3fe43dcd7b51442dc18754dcfe37c02ed1e8db42db2113d69ea60670f66e1fac5bf6c61543587bc8a6096cfbfc9f02e038c8d853bffbdb9fdddda33e82cbe4a391424e62fcf6cf878f9a26ce15a0> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150722/e413121d/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150722/e413121d/attachment.gif>
