Here more than 20 issues remains for IoTivity 1.2.0. Please register Jira tickets after each company QA execution.
Assignees, Please fill in the target date for fix. Key Summary Assignee Plan IOT-1318 <https://jira.iotivity.org/browse/IOT-1318> Build failed for tizen platform Philippe Coval IOT-1317 <https://jira.iotivity.org/browse/IOT-1317> [RI][Observe] Client callback is not deleted when receive cancel response Ziran Sun IOT-1316 <https://jira.iotivity.org/browse/IOT-1316> [Security][Null Pointer Dereference]'dateTimeValue' Null pointer dereference Abhishek Pandey IOT-1315 <https://jira.iotivity.org/browse/IOT-1315> [Security][Null Pointer Dereference] 'attributeString' Null pointer dereference Abhishek Pandey IOT-1314 <https://jira.iotivity.org/browse/IOT-1314> [Security][Null Pointer Dereference] 'fanSpeedString' 'airSpeedString' Null pointer dereference Abhishek Pandey IOT-1312 <https://jira.iotivity.org/browse/IOT-1312> [Security][known vulnerable function] gets() function does not check for buffer length Chihyun Cho IOT-1311 <https://jira.iotivity.org/browse/IOT-1311> [Security][Null Pointer Dereference] 'clientResponse' is redundant or null pointer dereference Ziran Sun IOT-1310 <https://jira.iotivity.org/browse/IOT-1310> [Security][known vulnerable function] strcpy: Does not check for buffer overflows Ziran Sun IOT-1309 <https://jira.iotivity.org/browse/IOT-1309> [Security][Buffer Overflow] Invalid scanf field width limit Randeep Singh IOT-1308 <https://jira.iotivity.org/browse/IOT-1308> [Security][Buffer Overflow] scanf format string needs field width limit Randeep Singh IOT-1304 <https://jira.iotivity.org/browse/IOT-1304> [Security][Index Out of Bounds] Array gLightInstance accessed at index 1 Jee Hyeok Kim IOT-1302 <https://jira.iotivity.org/browse/IOT-1302> Thread-unsafe code in oicgroup.c Dave Thaler IOT-1301 <https://jira.iotivity.org/browse/IOT-1301> can't receive any callback message when DTLS handshake is failed. dongik Lee IOT-1300 <https://jira.iotivity.org/browse/IOT-1300> OCSeedRandom() semantics differ on Windows Dan Mihai IOT-1298 <https://jira.iotivity.org/browse/IOT-1298> More than 12 observers (client_mode) on a single resource on a single server causes any subsequent (>12) clients to segfault/crash. Ziran Sun IOT-1296 <https://jira.iotivity.org/browse/IOT-1296> Need to be able to use Sqlite that is available system-wide saurabh sharma IOT-1295 <https://jira.iotivity.org/browse/IOT-1295> mbedtls library should be downloaded with SECURED option saurabh sharma IOT-1291 <https://jira.iotivity.org/browse/IOT-1291> unittest [service/resource-encapsulation] - rcs_client_test : GetValidOCResourceTest() failing dongik Lee IOT-1261 <https://jira.iotivity.org/browse/IOT-1261> [RI] [SECURED] [OBSERVE] Observe does not work on Secured Resources, Server gets crashed (only secured resource, non secured works fine) Ziran Sun IOT-1252 <https://jira.iotivity.org/browse/IOT-1252> [IS] [Plugin] Error message shown from POST response is does not match with what was sent by resource Senthil Kumar G S IOT-1250 <https://jira.iotivity.org/browse/IOT-1250> [RE][Tizen] Resource State showing LOST_SIGNAL after Start Monitoring Jay Sharma IOT-1240 <https://jira.iotivity.org/browse/IOT-1240> [RI] [ObserveCancel] OCDoREsource() APi can not cancel observe Ziran Sun IOT-1182 <https://jira.iotivity.org/browse/IOT-1182> Do not make API config dependent Uze Choi 9/30 IOT-1187 <https://jira.iotivity.org/browse/IOT-1187> The "Documentation" web page has a typo: "referecence" Uze Choi 9/30 IOT-1107 <https://jira.iotivity.org/browse/IOT-1107> Erroneous response to multicast discovery request Habib Virji IOT-1073 <https://jira.iotivity.org/browse/IOT-1073> Platform-specific ifdefs littering the code makes portability cumbersome and error prone David Antler BR, Uze Choi From: ???(Uze Choi) [mailto:[email protected]] Sent: Wednesday, September 21, 2016 5:28 PM To: 'iotivity-dev at lists.iotivity.org' Subject: RE: [dev] [WebEx info] RE: [This Week] IoTivity Bug Triage Meeting for release. Hi All, Please find the meeting minutes for today?s CC given below. Participants: Uze Choi Samsung Ashwini Samsung Ashok Channa Samsung Highlights: ? Currently registered Defects should be specified for Fix Version/s field. If not specified, Uze will tag as IoTivity 1.2.0 for until this coming release. ? Security project still has items to be merged into git. It should be shared in public. (Todo: Ashwini) ? CoAP redirection implementation is not required for this release (Ashok) o Backward compatibility could be achieved if we put the payload versioning scheme in the next release. ? Ask to QA function whether QA activity can include the test with CTT tool. (Sungkyu, please check it) BR, Uze Choi From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of ???(Uze Choi) Sent: Wednesday, September 21, 2016 2:28 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] [WebEx info] RE: [This Week] IoTivity Bug Triage Meeting for release. Hi Maintainer/Feature developer, Please participate 1.5 hour later CC. This week IoTivity Bug Triage meeting schedule as follows. This Week. 1st CC - Time: 21 Sep (Wed) 16:00~17:00. KST (For Asia/Europe time zone people Attending) <https://openconnectivity.webex.com/openconnectivity/j.php?MTID=m1524c94f48d 7d2f49c388c0fbe2271cc> Join WebEx meeting Meeting number (access code): 928 011 229 Host key: 592524 Meeting password: 1234 https://openconnectivity.webex.com/openconnectivity/j.php?MTID=m1524c94f48d7 d2f49c388c0fbe2271cc 2nd CC - Time: 22 Sep (Thu) 9:00~10:00. KST (For Asia/North America time zone people Attending) - (21 Sep 17:00~18:00 PST) <https://openconnectivity.webex.com/openconnectivity/j.php?MTID=mff955063d5f fe45636471c4072ab2880> Join WebEx meeting Meeting number (access code): 929 849 054 Host key: 925470 Meeting password: 1234 https://openconnectivity.webex.com/openconnectivity/j.php?MTID=mff955063d5ff e45636471c4072ab2880 Next Week. Date&Time: 28 Sep (Wed) 16:00~17:00. KST (for Asia/Europe time zone people attending) Date&Time: 29 Sep (Thu) 9:00~10:00. KST (for Asia/North America time zone people attending) I requested the WebEX CC to OCF staff, you can find it from OCF OSWG calendar. Of course I?ll announce it also. BR, Uze Choi From: ???(Uze Choi) [mailto:[email protected]] Sent: Tuesday, September 06, 2016 7:07 PM To: iotivity-dev at lists.iotivity.org Subject: IoTivity Bug Triage Meeting for release. Hi Maintainer/Feature developer, I?d like to plan to have a weekly CC on every Wed. As the first CC for this coming release, I arranged time tomorrow as follows. Time: 7/9 (Wed) 16:00~17:00. KST (Asia/Europe) Time: 7/10 (Thu) 9:00~10:00. KST (North America) Please notify if you want to attend it. Otherwise I?ll close to set up slot. I?ll share the detail CC info tomorrow. BR, Uze Choi -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/d8792f47/attachment.html>
