Enable the testpilot extension on the profiling branch

NEW
Unassigned

Status

()

Firefox
General
5 years ago
5 years ago

People

(Reporter: Away for a while, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
See bug 823989.
Is Test Pilot actually being used for anything useful?  Can we just remove it?

(I fully admit that bug 719455 permanently soured me on Test Pilot.  It caused a bad memory leak that took 10 months to get fixed.)
From a newsgroup thread on the same topic: we should make building the extension or not an explicit decision. --enable-testpilot? If it were added to the "nightly" mozconfigs on mozilla-central and friends all of the opt builds would use it. Probably would need to add it to the l10n configs too.
(Reporter)

Comment 3

5 years ago
(In reply to comment #2)
> From a newsgroup thread on the same topic: we should make building the
> extension or not an explicit decision. --enable-testpilot? If it were added to
> the "nightly" mozconfigs on mozilla-central and friends all of the opt builds
> would use it. Probably would need to add it to the l10n configs too.

That would make sense to me, but let's first decide whether test pilot is needed at all.  Who owns it?
Gregg Lind owns it, AFAICT.
We use it in User Experience all the time.  So does AMO and SUMO.  

bug 719455 soured me on it as well, honestly, and I own the thing.  It was a sour experience for lots of reasons, that I hope are now resolved.

The codebase is old and creaky, and getting a fully updated version is on board for q1/q2 of this year.  The big resourcing challenge we have on it is how much effort to spend fixing it, and how much to spent forward building.
Blocks: 823638
You need to log in before you can comment on or make changes to this bug.