Hi Gregg, 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). P1 is reserved (for the time being) for certification blocking issues only. If it’s still confusing, and you need to create a JIRA ticket, just create the issue, assign to Uze Choi (release mgr) or myself if it’s a security issue, and don’t see the priority field… we’ll set priority when we disposition the issue. Thanks, Nathan From: Gregg Reynolds [mailto:d...@mobileink.com] Sent: Thursday, August 17, 2017 8:37 PM To: Heldt-Sheller, Nathan <nathan.heldt-shel...@intel.com> Cc: iotivity-dev@lists.iotivity.org Subject: Re: [dev] JIRA priority usage On Aug 17, 2017 10:26 PM, "Heldt-Sheller, Nathan" <nathan.heldt-shel...@intel.com<mailto:nathan.heldt-shel...@intel.com>> wrote: Hello IoTivity Devs, I know there are different ways to use the P1-P3 labels, but between now and when IoTivity 1.3.1 is tagged (i.e. IoTivity 1.3 passes CTT) I would like to request the following: 1) Any JIRA issue that will prevent Certification (a.k.a. IoTivity passing the CTT), please assign P1 2) Any JIRA issue that will NOT prevent Certification, please assign P2 or below ?? you mean "or above"?
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
