Mark's point is that sometimes there's a separate QA/QC team (in the case of this sprint, it's an awesome PIH volunteer named Cordt). That's an extra, higher level of testing than what happens during our regular ticket workflow.
And since we don't have a QA/QC team for OpenMRS generally, we obviously haven't modeled the "to-be-tested-by-QA-QC. Another option would be to approve the ticket and add a label for "needs-QA". Once that QA has happened, then remove the label and possibly reopen the ticket, or create a new ticket. -Darius On Fri, Feb 3, 2012 at 11:29 AM, Michael Downey <[email protected]> wrote: > Shouldn't a post-commit code review also be ensuring the code change > actually fixed the problem? > > Michael > > _________________________________________ > > To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to > [email protected] with "SIGNOFF openmrs-devel-l" in the body > (not the subject) of your e-mail. > > [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l] > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
