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

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#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
   Resolution:           |  Parent ID:
Actual Points:           |
       Points:           |
-------------------------+-------------------------------------------------

Comment (by gk):

 Okay, I think I am done with filing all the tickets. While looking at all
 the Mozilla bugs I realized that we might want to have a slightly
 different process next time mainly for two reasons:

 1) If we are switching to, say, ESR 45 we should get started as soon as
 possible fixing/neutering new features to test as much new patches in the
 one alpha we usually only have. Thus, it makes more sense to have the bug
 review 39-44 already done by then (and a lot of the resulting ticket
 prioritization). This way we can identify critical things earlier and
 react better to them making sure they get definitely into the alpha.

 2) Having the feature review (almost) in parallel with upcoming Firefox
 releases gives us the option to backport/develop fixes we may/could need
 for ESR 38 but Mozilla does not deem important enough for an ESR release.

 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.

 We won't save time this way but if all goes well we should have more time
 to get ESR 45 features fixed and tested for the alpha and if needed we
 would be able to plug holes in ESR 38 with little effort. Seems to be
 worth it I think.

 That could be part of a review-dev-docs-and-bugs-guide (including proper
 bug URLs (like the one in comment:7)) documented somewhere in our spec
 repo.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16090#comment:15>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs