Bug 36250

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 BugsAssignee: 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 Flags
Patch eric: review+

Adam Barth
Reported 2010-03-17 16:13:02 PDT
Change post-rollout to create-rollout and have it make a new bug instead of posting the rollout to the old bug.
Attachments
Patch (7.03 KB, patch)
2010-03-17 16:21 PDT, Adam Barth 		eric: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Adam Barth
Comment 1 2010-03-17 16:21:00 PDT
Created attachment 50969 [details] Patch
Eric Seidel (no email)
Comment 2 2010-03-17 16:31:39 PDT
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.
Adam Barth
Comment 3 2010-03-17 16:40:05 PDT
Committed r56133
Note You need to log in before you can comment on or make changes to this bug.