New issue
Advanced search Search tips

Issue 918193 link

Starred by 2 users

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 0
Type: Bug


Sign in to add a comment

[chromeperf2] Launch next version of chromeperf dashboard

Project Member Reported by benjhayden@chromium.org, Dec 28

Issue description

From https://github.com/catapult-project/catapult/issues/4461

The next version of the chromeperf dashboard is currently in a branch, untested, and deployed to a staging version.
Most of the code has been merged to the master branch with tests. This bug tracks merging the remaining code to master, plus a few more steps.

Components left to merge to master:

 * add alerts-section to chromeperf-app
 * chart-timeseries
 * chart-complex
 * pivot-table
 * chart-section
 * add chart-section to chromeperf-app
 * report-controls
 * report-table
 * report-template
 * report-section
 * add report-section to chromeperf-app

Other steps required to launch:

 * Fix blocking bugs
 * Write documentation
 * Link from legacy pages to spa
 * Link from spa to legacy pages
 * Merge v2spa.yaml into app.yaml and bin/deploy_v2spa into bin/deploy, deploy spa to '/'

Followup tasks such as working through feedback from users, deleting old code, and migrating to lit-element will be tracked in separate bugs.
 
Labels: -Pri-3 Pri-0
P3->P0 because this project needs to wrap up in Q1 as a first priority. 

If that means dropping some less important features, or leaving some bugs open, that's fine.

This bug should also list its blockers, assuming they've all migrated from github issues into Monorail too. 

Comment 2 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 865515

Comment 3 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 918198

Comment 4 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 918197

Comment 5 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 917908

Comment 6 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 917906

Comment 7 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 917904

Comment 8 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 917891

Comment 9 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 917866

Comment 10 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 917847

Comment 11 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 914090

Comment 12 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 896804

Comment 13 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 894865

Comment 14 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 893237

Comment 15 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 893195

Comment 16 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 893193

Comment 17 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 893190

Comment 18 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 893189

Comment 19 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 892952

Comment 20 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 892951

Comment 21 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 892950

Comment 22 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 892949

Comment 23 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 892948

Comment 24 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 892947

Comment 25 by seanmccullough@chromium.org, Jan 16 (6 days ago)

Blockedon: 892946

Comment 26 by benjhayden@chromium.org, Today (11 hours ago)

Blocking: 924228

Sign in to add a comment