Hi Maintainers,
Ziran and Rick notices merge back status. Please share the status. Expecially,
Security Randeep, let us know.
I wish master branch get to be stabilized soon. At least I think All need to be
done by next week.
After All merge-back to master complete, Let?s commit and merge into master
first.
D&C project - CA Ashok
- RI Ziran (Early Next Week)
Security Project Randeep
Service Project JungYong
Cloud Project Jihyeok
Platform Extension-Windows Dave
-Android Rick (Done)
-Tizen Phil
Unit Test and Script Phil
From: Bell, Richard S [mailto:[email protected]]
Sent: Friday, December 09, 2016 5:11 AM
To: Ziran Sun; '??? (Uze Choi)'; iotivity-maintainers at lists.iotivity.org
Cc: iotivity-dev at lists.iotivity.org
Subject: RE: [Iotivity-maintainers] [Merge Back request] FW: IoTivity 1.2.1
Release announcement
Uze,
I confirm with my team that all android changes in 1.2-rel patches have been
merged back into master branch.
There were no changes to upnp in 1.2-rel patches.
Thanks,
-Rick
From: iotivity-maintainers-bounces at lists.iotivity.org
[mailto:[email protected]] On Behalf Of Ziran Sun
Sent: Thursday, December 8, 2016 4:19 AM
To: '??? (Uze Choi)' <uzchoi at samsung.com>; iotivity-maintainers at
lists.iotivity.org
Cc: iotivity-dev at lists.iotivity.org
Subject: Re: [Iotivity-maintainers] [Merge Back request] FW: IoTivity 1.2.1
Release announcement
Hi Uze,
There are a few from RI side are not in master yet due to merge conflicts. The
patch authors have been informed. We hope to have all in early next week. Hope
it?s okay.
Best regards,
Ziran
From: iotivity-maintainers-bounces at lists.iotivity.org
[mailto:[email protected]] On Behalf Of ??? (Uze
Choi)
Sent: 08 December 2016 04:55
To: iotivity-maintainers at lists.iotivity.org
Cc: iotivity-dev at lists.iotivity.org
Subject: Re: [Iotivity-maintainers] [Merge Back request] FW: IoTivity 1.2.1
Release announcement
Hi Maintainers (Ashok, Ziran, Randeep, Jungyoungm Jihyeok, Dave, Rick, Phil)
Could you confirm 1.2-rel patches are merged back into master branch?
If not now, let me know the target date to be finalized.
D&C project - CA Ashok
- RI Ziran
Security Project Randeep
Service Project JungYong
Cloud Project Jihyeok
Platform Extension-Windows Dave
-Android Rick (UPnP together)
-Tizen Phil
Unit Test and Script Phil
BR, Uze Choi
From: ??? (Uze Choi) [mailto:[email protected]]
Sent: Wednesday, December 07, 2016 6:08 PM
To: iotivity-maintainers at lists.iotivity
Subject: RE: [Merge Back request] FW: IoTivity 1.2.1 Release announcement
Let me ask the status per each sub project soon.
Please check the status first.
BR, Uze Choi
From: ??? (Uze Choi) [mailto:[email protected]]
Sent: Friday, December 02, 2016 3:48 PM
To: iotivity-maintainers at lists.iotivity
Subject: [Merge Back request] FW: IoTivity 1.2.1 Release announcement
Hi All,
Please merge back into master on 1.2-rel.
It should be done correctly with maintainer responsibility, but sometime there
are missing patch on master.
FYI, ISG is now considering the auto merge back mechanism from release branch
into master.
BR, Uze Choi
From: ??? (Uze Choi) [mailto:[email protected]]
Sent: Friday, December 02, 2016 2:33 PM
To: 'iotivity-dev at lists.iotivity.org'
Subject: IoTivity 1.2.1 Release announcement
Dear All,
Let me announce the 1.2.1 release.
We are expecting that product with IoTivity 1.2.1 can pass the OCF
certification with CTT(Certification Testing Tool) v1.4 (coming soon)
Tag : 1.2.1 ( <https://gerrit.iotivity.org/gerrit/#/admin/projects/iotivity>
iotivity.git)
Please use 1.2.0 tag for
<https://gerrit.iotivity.org/gerrit/#/admin/projects/iotivity-upnp-bridge>
iotivity-upnp-bridge.git
Wiki : https://wiki.iotivity.org/release_note_1.2.1
There is one test case fail from following test result from IoTivity QA (see
below mail)
However, it was figured out that this fail is not IoTivity issue but CTT tool
issue which will be updated soon.
BR, Uze Choi
From: iotivity-dev-bounces at lists.iotivity.org
[mailto:[email protected]] On Behalf Of ???
Sent: Friday, December 02, 2016 11:38 AM
To: iotivity-dev at lists.iotivity.org
Subject: [dev] CTT 1.3.21 vs. IoTivity 1.2-rel branch
Dear All,
Here is the test result between CTT 1.3.21 and IoTivity 1.2-rel branch.
- 1.2-rel latest + https://gerrit.iotivity.org/gerrit/#/c/14621/ (It's
already merged)
There is only 1 issue now and I think it can be resolved with next CTT ver.
TC
Error Log
Status
CT1.1.1 (Server Only )
cid:BEI0XT4NZ5JE at namo.co.kr
cid:2LL5XOK0LK7C at namo.co.kr
New, Collection only
From: ??? (Uze Choi) [mailto:[email protected]]
Sent: Thursday, December 01, 2016 3:08 PM
To: 'iotivity-dev at lists.iotivity.org'; 'cert_wg at openconnectivity.org';
'oswg at openconnectivity.org'
Subject: [IoTivity 1.2.1 release Schedule notification] : [oswg] CTT 1.3.20 vs.
IoTivity 1.2-rel branch
Hi All,
For the IoTivity 1.2.1 release, we may need one more day for testing against CTT
As reported below, Iotivity has bugs in the collection logic and /d, /p
resource also.
IoTivity QA team will test with the latest CTT 1.3.21 and the fixed version
again.
If there is no issue found from IoTivity side, IoTivity will release the 1.2.1
version promptly.
BR, Uze Choi
-------------- next part --------------
HTML ?????? ??????????????...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161209/5a5e24a4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7739 bytes
Desc: ?????? ?? ????????.
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161209/5a5e24a4/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 18558 bytes
Desc: ?????? ?? ????????.
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161209/5a5e24a4/attachment-0001.png>
