Confirmed users
95
edits
TestEngineering/Performance/Talos/RegressionBugsHandling: Difference between revisions
TestEngineering/Performance/Talos/RegressionBugsHandling (view source)
Revision as of 18:16, 9 February 2015
, 9 February 2015added requirement for 3 days response and links to performance sheriffing
m (minor edit) |
(added requirement for 3 days response and links to performance sheriffing) |
||
| Line 5: | Line 5: | ||
* Whoever landed the patch is responsible to drive a decision on whether or not the regression is acceptable. | * Whoever landed the patch is responsible to drive a decision on whether or not the regression is acceptable. | ||
* Such decision should preferably involve a module owner/peer of the regressed module. | * Such decision should preferably involve a module owner/peer of the regressed module. | ||
* | * The owner of the offending patch must respond at the bug within [https://groups.google.com/forum/#!searchin/mozilla.dev.platform/joel$20regression/mozilla.dev.platform/HkfaOTtAFVo/6L1E9GiOGGIJ 3 business days], and a decision has to be made within two weeks, otherwise the offending patch may be backed out. | ||
=====If the decision was to try and fix the regression, preferably a time frame and an owner would be provided as well.===== | =====If the decision was to try and fix the regression, preferably a time frame and an owner would be provided as well.===== | ||
| Line 26: | Line 26: | ||
The bottom line is that we want a visible decision on each case where the cause for the regression is known. | The bottom line is that we want a visible decision on each case where the cause for the regression is known. | ||
====See also==== | |||
* [https://wiki.mozilla.org/Buildbot/Talos/Sheriffing Regression sheriffing] - how are regressions detected and associated with patches. | |||