Hello IoTivity-Dev and OSWG Security TG, As we begin testing with CTT, I expect the JIRA ticket count to spike quickly. In order to make sure that no issues are lost, please ensure the following 3 things are set on any JIRA issues related to security that must be fixed before 1.3.0 release:
1) Add label "security" 2) Set "Fix In Version" to 1.3.0. 3) Set Priority to P1 If the issue doesn't show up in the following query, and it's security-related, it may not get fixed/included in 1.3.0: All Open, In Progress, Reopened, Assigned issues with "security" label, P1, and Fix In Version 1.3.0<https://jira.iotivity.org/issues/?jql=project%20%3D%20IOT%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20Assigned)%20AND%20priority%20%3D%20P1%20AND%20fixVersion%20%3D%20%22IoTivity%201.3.0%22%20AND%20labels%20%3D%20security%20ORDER%20BY%20priority%20DESC%2C%20created%20DESC> Also (and this applies to non-security issues as well), please try to include as much information as possible to help reproduce the issue, including: 1) Exact commit hash of IoTivity build used 2) Compile flags for build used 3) Execution steps (e.g. command lines issued and app steps selected) 4) If using CTT, CTT version #, and PICS file attached 5) If a particular CTT test failure, copy/paste the TC or reference the Test Requirements TC # and doc version Without this info we'll spend a lot of precious time asking for these details or trying to guess/check. Thanks for your help in getting us through QA and bug fix as quickly as possible, Nathan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170517/70529efc/attachment.html>
