[Webkit-unassigned] [Bug 36250] Change post-rollout to create-rollout and have it make a new bug instead of posting the rollout to the old bug.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Mar 17 16:31:39 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=36250
Eric Seidel <eric at webkit.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #50969|review? |review+
Flag| |
--- Comment #2 from Eric Seidel <eric at webkit.org> 2010-03-17 16:31:39 PST ---
(From update of attachment 50969)
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.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list