All,
IOT-2539<https://jira.iotivity.org/browse/IOT-2539> - Remove compiler warnings 
Linux

George has done a lot work in getting cleaning up all the compiler warnings and 
has finally completed this task.
This will help us in requiring the developers to provide solid code and get us 
out the business of cleaning up code.

Please review the final patch so that we can enable failures on warnings 
https://gerrit.iotivity.org/gerrit/#/c/22811/.

We would like this turned on going forward for the RC5 Tag.

Thanks,
-Rick Bell




From: iotivity-dev-boun...@lists.iotivity.org 
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Heldt-Sheller, 
Nathan
Sent: Monday, October 23, 2017 10:04 AM
To: abith...@samsung.com; iotivity-dev@lists.iotivity.org
Subject: Re: [dev] P1 Pending Issues and CTT Open Issues for 1.3.1 release

Mitch and I worked over the weekend, and resolved some of these issues already 
(they’re awaiting verification from QA who is on holiday at the moment).

There are actually at this point just (2) open Security issues that don’t 
already have fixes awaiting review: IOT-2829 and IOT-2830, both of which are 
new as of 3 days ago, and both of which are actively being worked on.  I expect 
them to be resolved within a few days.

Until these are fixed we can’t certify IoTivity and since RC4 tag was made, 
we’ll now need to make an RC5 tag when all issues are resolved.

Thanks,
Nathan

From: 
iotivity-dev-boun...@lists.iotivity.org<mailto:iotivity-dev-boun...@lists.iotivity.org>
 [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of ABITHA S
Sent: Monday, October 23, 2017 8:01 AM
To: iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org>
Subject: [dev] P1 Pending Issues and CTT Open Issues for 1.3.1 release


Dear All,



1.3.1-RC4 tagging is complete.



Please find below the current status of Open issues.

Kindly update the estimated Closure date and Status/blockers for the same.
Pending P1 Issues

Security

6

Alljoyn 
Bridge<https://jira.iotivity.org/issues/?jql=project+%3D+IOT+AND+component+%3D+%22Alljoyn+Bridge%22>

1

Total

7

CTT Bugs Count



1




and below is the summary of the current list of P1 issues captured from 
Iotivity Jira.


Issue key

Summary

Assignee

Priority

Status

Found in Version

Component/s

Status

1

IOT-1738

AllJoyn Bridge implementation

todd.malsbary

P1

Assigned

1.3-rel

Alljoyn Bridge

Pending testing with updated CTT tool

2

IOT-2726

/cred Resource handler updates rowneruuid sporadically

i.mushfiq

P1

In Progress

1.3.1-RC1

Security

Pending QA verification

3

IOT-2802

/roles Resource contains unexpected number of entries

mkettrick

P1

In Progress

1.3.1-RC2

Security

CTT updation in progress

4

IOT-2806

CT1.7.12.1 - RESET does not set the "tm" bits correctly

nathanheldtsheller

P1

In Progress

1.3-rel

Security

Pending verification

5

IOT-2821

CT1.7.8.11 - DOXS should have implicit access to /cred and /acl2 in RFOTM

phg

P1

In Progress

1.3-rel

Security

Pending QA verification

6

IOT-2829

CT1.7.8.11 - Access to Vertical Resources is only allowed in RFNOP

nathanheldtsheller

P1

Open

1.3-rel

Security

Pending status update

7

IOT-2830

CT1.7.8.11 - CMS cannot establish secure connection

danmihai

P1

In Progress

1.3-rel

Security

Patch is in code review.




And Below the list of CTT bugs pending for Affected Version set to Amsterdam


Bug ID

Product

Component

Assignee

Status

Summary

1

1397

OCF (public)

CTT

c...@openconnectivity.org<mailto:c...@openconnectivity.org>

UNCONFIRMED

Create a schema file to represent the allowable enumerations in the SH Device 
spec




Regards,

Abitha

[cid:image001.png@01D34C27.5265B8B0]

[http://ext.samsung.net/mail/ext/v1/external/status/update?userid=abitha.s&do=bWFpbElEPTIwMTcxMDIzMTUwMDMwZXBjbXM1cDQzMzYxM2NmN2I3M2M3ODkyOWFhZDNiMWUyNmM4YjRhNyZyZWNpcGllbnRBZGRyZXNzPWlvdGl2aXR5LWRldkBsaXN0cy5pb3Rpdml0eS5vcmc_]
_______________________________________________
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev

Reply via email to