June and Thiago, BTW, test engineering has been very aggressive in ramping. They have already started automated testing on the CA branch. Someone from test engineering should speak to the results to date. However, there are blocks of tests that work on master that do not work on the CA branch. The biggest set are ?ACK request? (confirmable) which is still not supported in the CA.
So, this is the order of delivery: 1) Feature complete 2) Fully reviewed 3) Unit tested (not system tests) 4) Acceptable (meaning good enough) testing engineering report 5) Ready to merge NOTE: I do not plan to accept JIRA tickets in place of missing/broken features that worked on master. Pat From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of Lankswert, Patrick Sent: Tuesday, March 24, 2015 9:16 AM To: juney at samsung.com; Macieira, Thiago; iotivity-dev at lists.iotivity.org Subject: Re: [dev] Fwd: Re: Re: [Request for feedback] IoTivity 0.9.1 Release Schedule & Feature June, It will be done when it is done. I would like to see it happen sooner. We still have a lot of issues to address. Unless I stop accepting any feature commits today, we are going to end up pushing the date out. Pat From: [email protected] <mailto:iotivity-dev- bounces at lists.iotivity.org> [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of ??? Sent: Tuesday, March 24, 2015 6:36 AM To: ???; Macieira, Thiago; iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] Fwd: Re: Re: [Request for feedback] IoTivity 0.9.1 Release Schedule & Feature Hi Pat, Thiago is saying that CA branch merge will not be completed by end of March. Is there any issue in merging CA branch since I'm suggesting first QA entry version should be release on 4/6 and exit from QA on 4/24. Actually, 0.9.1 is doesn't necessarily include IPv6 or something. Regards June June Yong Young Principal Engineer IoT Solution Lab. | Web & Convergence Team Software R&D Center, Samsung Electronics Co.,Ltd. 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-03-24 19:21 (GMT+09:00) Title : Re: Re: [dev] [Request for feedback] IoTivity 0.9.1 Release Schedule & Feature Thiago, Please find my answer in blue. Regards June June Yong Young Principal Engineer IoT Solution Lab. | Web & Convergence Team Software R&D Center, Samsung Electronics Co.,Ltd. T: +82-31-301-6107, M: +82-10-9530-6107 E-mail :juney at samsung.com ------- Original Message ------- Sender : Thiago Macieira<thiago.macieira at intel.com <mailto:thiago.macieira at intel.com> > Date : 2015-03-23 13:38 (GMT+09:00) Title : Re: [dev] [Request for feedback] IoTivity 0.9.1 Release Schedule & Feature On Monday 23 March 2015 03:50:07 ??? wrote: > > This is the announcement for IoTivity 0.9.1 release schedule in April. > > (IoTivity 1.0.0 is to be released as full compliant of the Spec in around > > Sep./Oct. timeframe according the direction of BoD.) _Please let us know > > your opinion about the schedule and confirm the features to be applied in > > April release._ > > Hi June > > Would you mind creating a wiki page with the the release criteria that you > have in your presentation? > -> Sure, I'll do that after the discussion will be finalized between Intel & > Samsung. Actually it is still being discussed in between 2 QA teams. Thanks! The QA teams should also post their conclusions to the mailing list. It would be especially helpful if they create a wiki page describing how they will work, if there's any division of tasks, etc. > It would also be a good idea to make sure all entries in your spreadsheet > exist in JIRA, so we track them live in the bug tracker. Attachments to > email can't be updated. The sheet "Platform support" also needs a glossary > -- I think I can guess what CA, TM and NM are, but I'm at loss over PPM and > SSM. -> PPM is protocol plug-in manager, SSM is Soft Sensor manager. > I think your suggestiion is good idea, but if feature list is too many, > it may be difficult for me to upload all of the list one by one in JIRA. It > is better to upload the feature has an issue only. Sorry, I disagree. We have to start somewhere. If we don't start now, we will always be in the position that the spreadsheet is too big. We should try and always *reduce* the spreadsheet until we no longer need it. I recommend you & George (Planning) start with the big features, the ones we really want in the release. The rest can be left for later. > Was the bottom part of your email a copy & paste from the spreadsheet? The > mailing list destroyed all formatting, so no one can read it. > -> Oh it has been corrupt? It has been just copy&paste from spreadsheet > anynow, so you can see in the spreadsheet. The mailing list drops the HTML formatting. Anything you pasted that required tables, colours, bold/italic, etc., is lost by the time others receive it. -> [June] Can I ask you something? Some mails through mailing list doesn't drop HTML formatting, but some email become corrupt. Do you perhaps know why? Droping HTML formatting is too inconvient. > 1) for this plan to hold, when is the latest that CA BRANCH can be merged > into the master branch? Shall we say one week before QA entry? That means > that if we get to March 30 and CA isn't merged yet, the plan will need > revising. > -> This is somewhat different from what I've been told. It is > targetting end of March and I'll check. I made an educated assumption: CA branch, as big as it is, will require one week of stabilisation in the main branch before we even consider starting the QA work and feature freeze. I might be wrong, and it might be that you consider that part of the work QA's job. My point is was to ask when said date is. When is the last moment that CA can be merged for your plan to hold? -> [June] I think 3/30 can be last day in order to release to QA. > 2) the same question applies to all of the other features: when is the > feature freeze date? Follow-up question: are we doing a feature-based > release or a time-based release? > -> CA is definitely feature-based because this is a kind of the purpose of > this release. But the rest of the features can be time-based. -> [June] One thing important is missing. 0.9.1 should be released as vA Compliant pre-release, so vA compliant has to be checked. If there are too many gaps against vA, then I cannot release 0.9.1 Thanks! But when is feature freeze? The date of QA entry? -> [June] I'm proposing the date of QA entry is 4/6 at present, but I haven't received a feedback from George yet. > 3) Are you talking about IP-over-Bluetooth support when you say BT/BLE > support? Or are you talking about OIC profile over Bluetooth? If you meant > the latter, I don't see how we can get it ready in 3 weeks since the > research to implement that is still ongoing. > -> I meant OIC profile over Bluetooth. Strange about your comment because > BT/BLE was in CA branch as a pre-release since 0.9.0. I'll check this out. I might be mistaken, but I thought someone on Bernie's team was researching it. But are you sure CA does OIC-profile-over-BT, not IP-over-Bluetooth? -> [June] For 0.9.1 release, BT/BLE support in CA branch is not definitely related to IP. BTW, what do you mean by IP-over-Bluetooth exactly? Is Intel working on IPv4 over BT? or Bluetooth4.2 IPSP? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center <http://ext.samsung.net/mailcheck/SeenTimeChecker?do=a89e2f31c590267ae0e8f14 c40c53e9447dd04bf706b32a4c13f49ee879cb6cf65afe93a9dd766927f71ac62d5c138b2195 f377979c7bbe51b20909a04efd4d2748cfe1d4e847419cf878f9a26ce15a0> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150324/198f0ce5/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/20150324/198f0ce5/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 7198 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150324/198f0ce5/attachment.p7s>
