Migrate ChromeDriver to use chromium bugs |
|
Issue descriptionThe merge process for pushing changes to release branches requires a chromium bug. We have to do merges ChromeDriver for go/chromedriver-versioning. For this reason, we would like to move ChromeDriver from having its own Monorail project ( https://bugs.chromium.org/p/chromedriver/issues/list ) to just using a component within chromium Monorail project. This requires a few changes: 1. Decide on a ChromeDriver component. We can re-use Tests>WebDriver. 2. Make an announcement to ChromeDriver users. 3. Somehow redirect people filing bugs in the old site to use the chromium component instead. 4. Do a mass migration of bugs from ChromeDriver project to chromium project. 5. Make chromedriver monorail project readonly.
,
Sep 28
I'll set up a meeting so get familiar with this and get the information I need to complete it.
,
Sep 28
One change that will be necessary is in Step 2 of the new issue wizard (see attached screenshot). We need to add ChromeDriver as a choice in there. It should map to component Tests>WebDriver.
,
Sep 28
Another change that would be very useful (if possible to implement): Automatic redirect from https://bugs.chromium.org/p/chromedriver/issues/list to https://bugs.chromium.org/p/chromium/issues/list?q=component%3ATests>WebDriver |
|
►
Sign in to add a comment |
|
Comment 1 by crouleau@chromium.org
, Sep 28Status: Assigned (was: Available)