June, Sure. Just to be sure, aren?t we using lower case tags now? So should it be ?0.9.1-rc1??
Pat From: ???(June Yong Young) [mailto:ju...@samsung.com] Sent: Tuesday, May 26, 2015 7:04 AM To: Lankswert, Patrick; Agrawal, Sachin; iotivity-dev at lists.iotivity.org; '???'; '???' Subject: RE: [dev] 0.9.1 release schedule Hi Pat, What is your progress? Uze has finalized Samsung code now, so you can tag ?0.9.1-RC1? now if Intel code is finalized. Regards, June 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: JuneYong Young [mailto:ju...@samsung.com] Sent: Monday, May 18, 2015 2:21 AM To: ???; Agrawal, Sachin; Lankswert, Patrick; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>; ???; ??? Subject: Re: [dev] 0.9.1 release schedule To all, I've slightly revised some items below after discussion with Samsung QA. - 0.9.1 : ?Spec vA Mandatory features? - Schedule . 5/20, Feature complete & Review Complete and make "0.9.1-RC1" release to QA . 5/25, QA reports back. . 5/26, "0.9.2-RC2" release just in case there an issue occurs on basic functionality . 5/28, QA to run Sanity check (about only the issue items) . 5/29, Website Open - Mandatory items must be completed . Any basic functionality should be working . Merge CA(connectivity Abstraction) branch onto one master branch - The items strongly requested, but no gating issues to release . BT/BLE Support, Noti. Manager, Android API . If any issues related to these items, they will be described as known issues. - QA . P1 problems to be fixed. If it is not fixed, then it has to be lowered down to P2 after discussion with QA. To Pat, George is a release manangement function counter part of Intel side. Please check with Intel QA since George is not present now. Regards June 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 ------- Original Message ------- Sender : ???<juney at samsung.com<mailto:juney at samsung.com>> S6(??)/??/IoT Solution Lab(S/W??)/???? Date : 2015-05-15 11:40 (GMT+09:00) Title : [dev] 0.9.1 release schedule To all, According to the discussion result in the last ISG & OSWG F2F meeting, we will release & open 0.9.1 at the end of May with schedule driven. So, 0.9.1 will be released based on the following. If any questions or concerns, then let us know. - 0.9.1 : ?Spec vA Mandatory features? - Schedule . 5/22, Feature complete & Review Complete . 5/28, exit from QA . 5/29, Website Open - Mandatory items must be completed . Merge CA(connectivity Abstraction) branch onto one master branch - The items strongly requested, but no gating issues to release . BT/BLE Support, Noti. Manager, Android API - QA . P1 problems to be fixed. If it is not fixed, then it has to be lowered down to P2 after discussion with QA. [cid:image001.png at 01D0979A.3BF73980] 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:iotivity-dev-bounces at lists.iotivity.org> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Agrawal, Sachin Sent: Friday, May 15, 2015 8:30 AM To: Lankswert, Patrick; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Last call for contributions for 0.9.1 Hi Pat, Can you clarify this statement? ?Failing to do so will result in your contribution being held until the next release? My assumption is that ?master? will still be open for code check-ins, except that the check-in?s after May 28th will NOT be tagged for 0.9.1 release. Is that right? Thanks Sachin 503-264-8071 From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Lankswert, Patrick Sent: Wednesday, May 13, 2015 2:21 PM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] Last call for contributions for 0.9.1 To all, The following dates are important for the 0.9.1 release: June 5th ? Code Freeze May 28th ? Feature Complete and Review Complete It is important that contributions be completed by May 28th, so that system testing may start. If you have a contribution that you want considered for 0.9.1 that is not already in gerrit review, you must announce on this list with an estimated date for your submission. Failing to do so will result in your contribution being held until the next release. We are working on a more formal release schedule process what will be published on the wiki. Pat Patrick Lankswert Discovery and Connectivity (Core Stack) Maintainer [cid:image002.gif at 01D0979A.3BF73980] [http://ext.samsung.net/mailcheck/SeenTimeChecker?do=c7ba9f2f7185d6393c28b3c940eb11c25a9f8d8a74e3363d87dfe03c47d8dbcb08c5ce1bd480a15cd4a87a1fb2ad96504bea3c1765014a1208cece8541bc14eacf878f9a26ce15a0] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150526/e6bb4037/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 141688 bytes Desc: image001.png URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150526/e6bb4037/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 13168 bytes Desc: image002.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150526/e6bb4037/attachment.gif>
