I'd like to see add-on developers who are registered with AMO be able to submit development versions of their extensions to a try-server that only does performance testing. The flow might look something like this: 1. dev has an xpi that they'd like to see perf numbers for 2. they go to a page on AMO in the developer hub, and upload their xpi 3. AMO sends the xpi to the try-server 4. the try-server gets the latest active release of Firefox, creates a profile, installs the extension into it 5. the try-server runs the full suite of performance tests 6. the try-server posts the results back to an AMO web service endpoint 7. the AMO web service emails the results to the add-on developer (6 & 7 could be removed if AMO sent the email along with xpi, and try-server emailed the results directly to the developer)

Still finalizing Q2 2010 goals, but this may make the list.

Is this a DUP of bug#599169 ?

Bug 599169 has the full dependency tree for this.