| Summary: | Commit queue for security bugs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Daniel Bates <dbates+webkittest> | ||||
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | NEW --- | ||||||
| Severity: | Normal | CC: | aakash_jain, ap, dbates, lforschler, nowlast878, rniwa, ryanhaddad, youennf | ||||
| Priority: | P2 | ||||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Bug Depends on: | 186817, 186834 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Daniel Bates
2018-06-19 22:02:16 PDT
One idea to support this functionality is to take a similar approach as was taken in bug #186291. If we can assume that the security-sensitive patch was uploaded to the status server by the EWS for security bugs machinery added in bug #186291 then to add commit-queue support for such patches it should be sufficient 1) teach the Bugzilla extension how to CC the commit-queue feeder EWS on security bugs and 2) teach the commit-queue feeder machinery how to fetch patches from the status server. Created attachment 344096 [details]
Images
Security bugs |