| Summary: | Change post-rollout to create-rollout and have it make a new bug instead of posting the rollout to the old bug. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Adam Barth <abarth> | ||||
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | eric | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Other | ||||||
| OS: | OS X 10.5 | ||||||
| Attachments: |
|
||||||
|
Description
Adam Barth
2010-03-17 16:13:02 PDT
Created attachment 50969 [details]
Patch
Comment on attachment 50969 [details]
Patch
period:
12 but we might revist this question in the future
You need to explain this better. "createBug" is the problem step here, no?
295 # We're not going to post the rollout patch to the old bug. Instead,
296 # we're going to create a new bug that blocks the original bug.
297 state["bug_blocked"] = state["bug_id"]
298 del state["bug_id"]
This also doesn't help:
299 # Now that we've danced around the bug_id issue, we can fill out the
300 # details for the new bug we're going to create.
"danced around?"
(if we don't already have one on file)
We need a FIXME about linking possible bugs here. We certainly have that technology (or could build it).
How do you spell "flaky"? And "dup"?
Otherwise fine.
|