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 We've gone through the existing JIRA issues and tried to apply this rule. We're relying on this to make sure that a) no CTT-blockers slip by un-noticed and b) no other issues are mistakenly getting worked on until all the CTT-blockers are finished. Please help out by making sure any ticket you submit that is going to cause Cert failure gets a P1 assigned, and do not use P1 for any other issues than these. Christian, we can discuss whether this is the right policy longer term, and if so add to the wiki page on JIRA usage (https://wiki.iotivity.org/jira_how_to_use). Thanks, Nathan
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
