Bug 91658
| Summary: | "Re-opened since this is blocked" is a wrong policy | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | abarth, dpranke, eric |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Alexey Proskuryakov
I'm seeing sheriffbot re-open a bug when a rollout is created. Such policy is not very helpful - the original bug should not be re-opened unless a rollout is actually landed, which doesn't always happen. Can commit queue do this instead?
The current situation is highly confusing, and makes one need to remember to re-close a bug if the regression is fixed in a different way.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |