1.2.0-RC2 on 1.2-rel branch has been tagged on iotivity repo. (1.2-rel branch is created)
Related on 1.2.0 please commit on the 1.2-rel branch first and cherrypick into master together. From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ???(Uze Choi) Sent: Wednesday, August 31, 2016 7:40 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] [RC1 Tagged] RE: Detail Timeline for IoTivity 1.2 Release 1.2.0-RC1 on master branch has been tagged on iotivity repo. From: ???(Uze Choi) [mailto:[email protected]] Sent: Tuesday, August 30, 2016 11:11 AM To: 'iotivity-dev at lists.iotivity.org' Subject: [For RC1 Tagging - status update] RE: Detail Timeline for IoTivity 1.2 Release Due to recent drastic patches in the master, I noticed some implemented features does not work due to dependency. So that I failed to make the RC1 tag, I expect it will take one more day. If any issue such as basic operation fail for released feature, please continue to share the status. Once it has been resolved, I?ll make the RC1 tag. BR, Uze Choi (Release management Function Lead) From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ???(Uze Choi) Sent: Monday, August 29, 2016 1:33 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] [For RC1 Tagging] RE: Detail Timeline for IoTivity 1.2 Release Today I?m supposed to make the RC1 tag (on master branch) on iotivity repository. Let me announce the changeID candidate in advance sooner. Now I?m waiting some commits to resolve Windows build problem and some primitive service patches for some update. Rick, please make the tag for 1.2.0-RC1 on iotivity-upnp-bridge repo. and start the QA. 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) <http://v70ext.samsung.net/mail/ext/v1/external/status/update?userid=uzchoi&do=bWFpbElEPTIwMTYwODI0MTQwMzIyZXBjbXMxcDc1NWYwYTAzYzVmNWYwNTZmNTZlOWRhZDRjZWM2YTFhNSZyZWNpcGllbnRBZGRyZXNzPWlvdGl2aXR5LWRldkBsaXN0cy5pb3Rpdml0eS5vcmc_> -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160912/7d98c871/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13402 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160912/7d98c871/attachment.gif>
