Feature #7542
Decide whether we migrate to the Tor browser in time for FF31
100%
Description
The work needed to migrate to FF31 is very different, depending on whether we switch to Tor browser, or update our current custom package once again.
Subtasks
Related issues
Related to Tails - |
Resolved | 2014-09-10 | |
Blocks Tails - |
Resolved | 2014-08-02 |
History
#1 Updated by intrigeri 2014-07-10 15:41:41
- Target version set to Tails_1.2
#2 Updated by intrigeri 2014-09-22 12:05:18
- blocks
Feature #7725: Isolate I2P web browsing from Tor added
#3 Updated by intrigeri 2014-09-22 12:11:13
- related to
Feature #7887: View online PDF inside the web browser by default added
#4 Updated by anonym 2014-09-25 16:22:14
So, given that the work I’ve done so in feature/tor-browser-bundle
, can we close this ticket with the answer “Yes, let’s do it!”?
#5 Updated by intrigeri 2014-09-25 18:29:10
> So, given that the work I’ve done so in feature/tor-browser-bundle
, can we close this ticket with the answer “Yes, let’s do it!”?
I’m tempted to say yes, but I think it would be more reasonable to do it only after having filed the tickets about what’s left to do.
#6 Updated by intrigeri 2014-09-27 09:28:03
- Status changed from Confirmed to Resolved
Let’s say we’ll go ahead, somehow :)
#7 Updated by intrigeri 2014-09-27 17:48:19
I should add: my main rationale for closing this ticket is that we have not started at all any kind of work to migrate to Iceweasel 31ESR, so going the TBB way seems to be safer, as the problems we may run into will be a bit more self-contained (as opposed to spread everywhere on the filesystem / dependency tree / etc.), and (hopefully) most of them will be dealt with already by the Tor Browser team.
#8 Updated by anonym 2014-10-02 15:38:15
- % Done changed from 0 to 100