Bug 36250 - Change post-rollout to create-rollout and have it make a new bug instead of posting the rollout to the old bug.
: Change post-rollout to create-rollout and have it make a new bug instead of p...
Status: RESOLVED FIXED
: WebKit
New Bugs
: 528+ (Nightly build)
: Other Mac OS X 10.5
: P2 Normal
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2010-03-17 16:13 PST by
Modified: 2010-03-17 16:40 PST (History)


Attachments
Patch (7.03 KB, patch)
2010-03-17 16:21 PST, Adam Barth
eric: review+
Review Patch | Details | Formatted Diff | Diff


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2010-03-17 16:13:02 PST
Change post-rollout to create-rollout and have it make a new bug instead of posting the rollout to the old bug.
------- Comment #1 From 2010-03-17 16:21:00 PST -------
Created an attachment (id=50969) [details]
Patch
------- Comment #2 From 2010-03-17 16:31:39 PST -------
(From update of attachment 50969 [details])
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.
------- Comment #3 From 2010-03-17 16:40:05 PST -------
Committed r56133