[tor-bugs] #16090 [Tor Browser]: Review Firefox Developer Docs and Undocumented bugs since FF31esr

[Tor Bug Tracker & Wiki]

#16090: Review Firefox Developer Docs and Undocumented bugs since FF31esr
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  mikeperry
  mikeperry              |     Status:  new
         Type:  task     |  Milestone:
     Priority:  normal   |    Version:
    Component:  Tor      |   Keywords:  ff38-esr, MikePerry201505,
  Browser                |  TorBrowserTeam201506, tbb-5.0a3-essential,
   Resolution:           |  MikePerry201506
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+-------------------------------------------------

Comment (by gk):

 Replying to [comment:16 mcs]:
 > Replying to [comment:15 gk]:
 > > What I have in mind would look like the following: As soon as we get
 our ESR 38 based Tor Browser out one of the team is catching up on the
 Firefox for developers documentation (this seems to cover the most
 important and most difficult to patch things and should therefore be
 enough for the first pass). Then we can review new features shortly after
 new Firefox versions get released (and think about fixing things for our
 ESR 38 based Tor Browser if needed). When we start preparations for ESR 45
 we basically have all the ff45-esr tickets filed, and ideally prioritized,
 resulting out of Firefox 39-44 feature reviews. What is needed on the
 review part then are only the news coming with ESR 45 and double-checking
 the undocumented bugs and the ones with milestone Firefox39-45.
 >
 > This is a good idea and should allow us to scope the work earlier for
 the next ESR release.  Should we make this part of the release procedures?
 How will we remember to do it?

 I thought about adding instructions to our tor-browser-spec repo in the
 audits folder describing the procedure: one of the team has the task of
 keeping track of the Firefox features and is filing the respective tickets
 and estimating their importance + tagging them with ffesr-45 (to take the
 example for the next release).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16090#comment:20>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online