Organize our patches and prepare for rebase

Before we rebase, we should see if we can reorganize our patches into better functional groups, and make a note of what in-tree tests currently fail before the switch.

added TorBrowserTeam201507 component::applications/tor browser ff38-esr owner::tbb-team priority::medium resolution::fixed status::closed tbb-5.0a3-essential type::defect labels

Trac:
Cc: N/A to brade, mcs

Trac:
Cc: brade, mcs to brade, mcs, arthuredelstein

Trac:
Cc: brade, mcs, arthuredelstein to brade, mcs, arthuredelstein, gk

Trac:
Cc: brade, mcs, arthuredelstein, gk to brade, mcs, arthuredelstein, gk, boklm

Trac:
Keywords: TorBrowserTeam201504 deleted, TorBrowserTeam201505 added

Trac:
Keywords: TorBrowserTeam201505 deleted, TorBrowserTeam201506 added

Tag the set of things we should aim to understand/fix for the fist FF38-based TBB (5.0a3, on June 30th).

Trac:
Keywords: N/A deleted, tbb-5.0a3-essential added

What needs still to be done for this ticket?

Trac:
Status: new to needs_information

Move over remaining June items to July

Trac:
Keywords: TorBrowserTeam201506 deleted, TorBrowserTeam201507 added

I think this can be closed. The patches are rebased. We may do some other things with them, but this ticket is too general. We already have other tickets for things like ensuring the tests work as expected and per-topic branches.

Trac:
Resolution: N/A to fixed
Status: needs_information to closed

closed

moved to tpo/applications/tor-browser#15579 (closed)