Opened 4 years ago

Closed 4 years ago

#15579 closed defect (fixed)

Organize our patches and prepare for rebase

Reported by: mikeperry Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Keywords: ff38-esr, tbb-5.0a3-essential, TorBrowserTeam201507
Cc: brade, mcs, arthuredelstein, gk, boklm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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.

Child Tickets

Change History (10)

comment:1 Changed 4 years ago by mcs

Cc: brade mcs added

comment:2 Changed 4 years ago by arthuredelstein

Cc: arthuredelstein added

comment:3 Changed 4 years ago by gk

Cc: gk added

comment:4 Changed 4 years ago by boklm

Cc: boklm added

comment:5 Changed 4 years ago by mikeperry

Keywords: TorBrowserTeam201505 added; TorBrowserTeam201504 removed

comment:6 Changed 4 years ago by mikeperry

Keywords: TorBrowserTeam201506 added; TorBrowserTeam201505 removed

comment:7 Changed 4 years ago by mikeperry

Keywords: tbb-5.0a3-essential added

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

comment:8 Changed 4 years ago by gk

Status: newneeds_information

What needs still to be done for this ticket?

comment:9 Changed 4 years ago by mikeperry

Keywords: TorBrowserTeam201507 added; TorBrowserTeam201506 removed

Move over remaining June items to July

comment:10 Changed 4 years ago by mikeperry

Resolution: fixed
Status: needs_informationclosed

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.

Note: See TracTickets for help on using tickets.