Hi IoTivity Feature developer/Maintainers.


The remaining jira issues for IoTivity 1.2.0 are as follows. (most of
issues are resolved/closed)

Only orange color has need to be discussed to exclude it from release scope
or not.

If needed it into 1.2 release, please attend to advocate it.

Criteria for release is no Major severity issue from Official QA test
report from RC tagging.

           and no OIC certification issue.


 <https://jira.iotivity.org/secure/IssueNavigator.jspa?requestId=11107> 1.2.
0 Filter (IoTivity)


Displaying 22 issues at 12/Oct/16 7:22 AM.


Issue Type

Key

Summary

Priority

Resolution

Due Date


Bug

 <https://jira.iotivity.org/browse/IOT-1429> IOT-1429

ACL Table update scheme fix

P1

Unresolved

??


Bug

 <https://jira.iotivity.org/browse/IOT-1442> IOT-1442

DevOwner needs SVR access after RFOTM

P1

Unresolved

Today


Bug

 <https://jira.iotivity.org/browse/IOT-1441> IOT-1441

DevOwner should not have implicit SVR access during Ready for Provisioning
State

P1

Unresolved

Today


Improvement

 <https://jira.iotivity.org/browse/IOT-1429> IOT-1429

Disable (D)TLS 1.0 and 1.1

P3

Unresolved

next?


Bug

 <https://jira.iotivity.org/browse/IOT-1422> IOT-1422

[SM] SceneMember Resource is not implemented as sm spec

P2

Unresolved

Today


Bug

 <https://jira.iotivity.org/browse/IOT-1421> IOT-1421

[SM] SceneCollection Resource is not implemented as sm spec

P2

Unresolved

Today


Bug

 <https://jira.iotivity.org/browse/IOT-1420> IOT-1420

[SM] SceneList Resource is not implemented as sm spec

P2

Unresolved

Today


Bug

 <https://jira.iotivity.org/browse/IOT-1419> IOT-1419

[RI] [Security] When a secured client tries to start dtls handshaking with
a secured server using invalid credential, the error response is of wrong
type

P2

Unresolved

Today


Bug

 <https://jira.iotivity.org/browse/IOT-1417> IOT-1417

[CS] [Linux] [CPP] Sign Up , Sing In and Sing Out Workflow Provide error in
Cloud Client SAmple App

P2

Unresolved

Today


Bug

 <https://jira.iotivity.org/browse/IOT-1406> IOT-1406

Trying to build IoTivity stack with unit tests on windows fails if SECURED=0

P2

Unresolved

next?


Bug

 <https://jira.iotivity.org/browse/IOT-1398> IOT-1398

CheckFunc() provides false negative on Windows x86

Undecided

Unresolved

Today


Task

 <https://jira.iotivity.org/browse/IOT-1380> IOT-1380

Use BCryptGenRandom instead of CryptGenRandom on Windows

Undecided

Unresolved

next?


Bug

 <https://jira.iotivity.org/browse/IOT-1370> IOT-1370

Callback context in OCResource API

Undecided

Unresolved

Looks resolved


Task

 <https://jira.iotivity.org/browse/IOT-1368> IOT-1368

handle Resource creation with Non secure option, in Secured=1 mode.

P1

Unresolved

Still

discussion


Task

 <https://jira.iotivity.org/browse/IOT-1367> IOT-1367

Multiple ownership transfer

P2

Unresolved

Today


Bug

 <https://jira.iotivity.org/browse/IOT-1359> IOT-1359

Assertion failed: it->type != CborInvalidType, file
extlibs\tinycbor\tinycbor\src\cborparser.c, line

P1

Unresolved

next?


Bug

 <https://jira.iotivity.org/browse/IOT-1300> IOT-1300

OCSeedRandom() semantics differ on Windows

Undecided

Duplicate

-


Bug

 <https://jira.iotivity.org/browse/IOT-1298> IOT-1298

More than 8 observers (client_mode) on a single resource on a single server
causes any subsequent (>8) createResource calls to fail.

P2

Unresolved

next?


Improvement

 <https://jira.iotivity.org/browse/IOT-1296> IOT-1296

Need to be able to use Sqlite that is available system-wide

P2

Unresolved

next?


Improvement

 <https://jira.iotivity.org/browse/IOT-1227> IOT-1227

Network status change should trigger OC_PRESENCE_TRIGGER_CHANGE event

P3

Unresolved

next?


Improvement

 <https://jira.iotivity.org/browse/IOT-1187> IOT-1187

The "Documentation" web page has a typo: "referecence"

P2

Unresolved

-


Improvement

 <https://jira.iotivity.org/browse/IOT-1182> IOT-1182

Do not make API config dependent

P2

Unresolved

-


Generated at Wed Oct 12 07:22:00 UTC 2016 by Uze Choi using JIRA 6.2.3#6260-
sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558. 



Please Attend the triage meeting as follows.

Wednesday, October 12, 2016  | 5:05 pm Pacific Daylight Time (GMT-08:05,
Thursday, October 12, 2016, 09:05 am KST)



https://openconnectivity.webex.com/openconnectivity/j.php?MTID=m0bf802d0332a
0c0352a75e0f407b3868

Meeting number: 920 027 145

Meeting password: 1234



BR, Uze Choi

-------------- next part --------------
HTML ?????? ??????????????...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161012/215fe097/attachment.html>

Reply via email to