As of now there are 39 Open issues for Priority P1. https://jira.iotivity.org/issues/?jql=status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20Assigned)%20AND%20priority%20%3D%20P1%20ORDER%20BY%20summary%20ASC
If any P2 or lower priority issues are to be P1 (OCF Cert blocker for 1.3.1 release), please update the priority, comments and description to help the release management and QA. To be able to prepare RC milestones for 1.3.1, we should see number of P1 tickets to be handled within next 5 days. I will be happy to help on Non-Security issues within my time bandwidth. Thanks to Nathan & Randeep for managing Security issues. Regards Dwarka ---------------------------------------------------------------------------------- Software R&D Center | Software Strategy Team | Open Source Group Open Connectivity Foundation (OCF) | Iotivity | Javascript Foundation (JSF) -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Saturday, August 19, 2017 12:49 AM To: [email protected] Subject: Re: [dev] JIRA priority usage On Friday, 18 August 2017 00:03:08 PDT Heldt-Sheller, Nathan wrote: > No, I really did mean P2 or below. > > For an issue that will not block certification, it’s okay to assign > P2, or a lower priority than P2 (e.g. P3). A lower priority has a higher number. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
