>From this week QA will be started, and bug will be registered into Jira.
>From the next week, I?ll set up the weekly call for Jira issue handling which >requires maintainers and feature contributors attending. If assigned defect is not handled yet, please update the status. BR, Uze Choi From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? Sent: Wednesday, August 24, 2016 11:03 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] Detail Timeline for IoTivity 1.2 Release As IoTivity noticed before, 1.2 release is supposed to be done by End of Sep. As a release management lead, let me announce the timeline for 1.2 release. This schedule has been already discussed with QA lead. 8/22~8/26 By this week, release feature candidates will be fixed. For each release feature, source code should exist on master and ready to open in public. 8/29~9/2 1st QA will be executed. (1.2-RC1 tag on master branch) ~9/9 1.2-rel branch will be created. 9/12~9/16 2nd QA will be executed. (1.2-RC2 tag on 1.2-rel branch) 9/26~9/30 3rd QA will be executed. (1.2-RC3 tag on 1.2-rel branch) ~9/30 1.2 release announce After gathering feature list, let me publish the policy for build build option and how to separate the header file as considering module dependency. Please update the configuration to align this policy. How QA to be done will be announced by QA lead sooner. BR, Uze Choi (Release Management Function Lead) -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160830/3cd909df/attachment.html>
