mozilla / testpilot

Test Pilot is a platform for performing controlled tests of new product concepts in Firefox
https://testpilot.firefox.com/
250 stars 123 forks source link

Delivery of all launch experiment details and assets #493

Closed pdehaan closed 8 years ago

pdehaan commented 8 years ago

Before we launch, we should make sure we audit the current Activity Stream info and make sure we list the correct measurements, contributors, version, and other data.

/edited by Cory

Master asset tracking document.

ckprice commented 8 years ago

Adding this to the 2016-04-22 milestone along with #438 which is related.

pdehaan commented 8 years ago

Ref: #555 "Refresh demo_data.json with up to date info"

After updating any Activity-Stream information in admin, we should make sure we update the demo_data.json fixture data to match.

lmorchard commented 8 years ago

After updating any Activity-Stream information in admin, we should make sure we update the demo_data.json fixture data to match.

In which admin? :) I'm not sure demo_data.json should actually match any particular environment. Data will differ between prod, stage, and dev depending on what kind of tests / research we want to run there.

demo_data.json is mainly there to offer some sample data to exercise features during local dev, not to replicate what might be in production. I originally loaded the new dev server with it to have something there, but it's not necessarily the best content to have there

lmorchard commented 8 years ago

(oops, didn't mean to close)

ckprice commented 8 years ago

I updated this a bit to address all 3 launch candidates (as well as updated Issue opening).

I also moved it out to the 2016-05-06 milestone, as the requirements for everything should be more clear next week (e.g. after landing #575, #438).

pdehaan commented 8 years ago

Updated activity-stream icon in https://github.com/mozilla/activity-streams/pull/544

pdehaan commented 8 years ago

Not exactly related, but this seems like the best place for this useless comment. Some of our pages are pretty beefy. We should make sure we're doing "our best"(tm) after we get our final launch assets in place:

PAGE REQUESTS PAYLOAD
http://testpilot.dev.mozaws.net/experiments 22 747 KB
http://testpilot.dev.mozaws.net/ (something's up) 19 741 KB
http://testpilot.dev.mozaws.net/?{token} 25 750 KB
http://testpilot.dev.mozaws.net/experiments/activity-stream 25 2,855 KB
http://testpilot.dev.mozaws.net/experiments/tabcenter 22 801 KB
http://testpilot.dev.mozaws.net/experiments/universal-search 27 3,040 KB

In some cases we're serving 1500x1000 px (800 KB) avatar photos (in case anybody else needs some high-resolution @chuckharmston wallpaper), or 1200x1200 px (600 KB) @nchapman avatar wallpaper, or else 2-3 screenshots which are 340-690 KB each.

lmorchard commented 8 years ago

In some cases we're serving 1500x1000 px (800 KB) avatar photos (in case anybody else needs some high-resolution @chuckharmston wallpaper), or 1200x1200 px (600 KB) @nchapman avatar wallpaper, or else 2-3 screenshots which are 340-690 KB each.

FWIW, this is also related to #46 - we don't have a built-in thumbnail facility on the site that processes uploads, so all images should be pre-scaled & optimized for whatever sizes they need to be.

ckprice commented 8 years ago

Shipped!