Feature #10194

Upgrade to Tor 0.2.7

Added by intrigeri 2015-09-15 01:30:30 . Updated 2015-11-03 11:30:12 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_1.7
Start date:
2015-09-15
Due date:
% Done:

100%

Feature Branch:
feature/10194-tor-0.2.7
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Subtasks

Feature #10195: Wait for Tor 0.2.7.x to be stabilized Resolved

100
Feature #10196: Test Tor 0.2.7.x in the context of Tails Resolved

100
Feature #10197: Rebuild Tor 0.2.7.x for wheezy-backports Resolved

100
Feature #10308: Use KeepAliveIsolateSOCKSAuth to drop custom Tor patch Resolved

100

History

#1 Updated by anonym 2015-10-16 08:09:31

  • Status changed from Confirmed to In Progress
  • Assignee set to anonym
  • Target version set to Tails_1.7
  • Feature Branch set to feature/10194-tor-0.2.7

intrigeri wrote on Feature #10197#note-6:
> > This looks quite promising, so if 0.2.7 is released in time for 1.7, perhaps we should try it?
>
> Now that you’ve done all this work, sure! Just ask nickm if we should ship 0.2.7.3-rc, and follow his advice?

From #tor-dev:

(16:29:59) dgoulet: anonym: [regarding the stability of the] next -rc, I don't know, nickm would have to answer this, but in term of stability, I'm quite unsure, I think 027 is pretty stable now and much better than 026 but that's always a hard call to recommend an -rc :)
[...]
(16:40:56) nickm: I think the latest RC is good enough.
(16:40:59) nickm: anonym: ^
(16:41:16) nickm: I'm going to put out another rc next week, which should have basically no changes.
(16:41:24) nickm: and i'm aiming for 1 nov for the stable release

So based on dgoulet’s optimism, and nickm’s wisdom, let’s include tor 0.2.7.x(-rc)? in Tails 1.7! We might as well get -rc3 merged ASAP, and then do another run of lazy testing (i.e. automated) for -rc4 (unless the changelog contains something surprising that requires extra attention/testing).

If the stable 0.2.7.x release indeed is out on 2015-11-01 (or earlier) we have the opportunity to get it into Tails 1.7 since I’ll build the image the next day. However, I will be AFK the 1st, so all would have to be done on the 2nd (a.k.a. image building day) unless someone else rebuilds it for wheezy-backports and tests it. If it would land on me, I’d, again, do lazy testing only, and look at the changelog for surprises.

#2 Updated by anonym 2015-10-16 08:19:06

Note: I have force pushed my feature/10194-tor-0.2.7-in-wheezy as feature/10194-tor-0.2.7. Your old one is still available as feature/10194-tor-0.2.7-in-jessie, but I’ll likely fix it up so it’s based on my branch instead.

#3 Updated by anonym 2015-10-17 05:40:46

  • Assignee deleted (anonym)
  • QA Check set to Ready for QA

#4 Updated by anonym 2015-10-22 06:51:10

  • Assignee set to bertagaz

#5 Updated by bertagaz 2015-10-25 03:04:39

  • Assignee changed from bertagaz to anonym

Reassigning to anonym like Feature #10197.

#6 Updated by anonym 2015-10-26 13:01:12

  • Status changed from In Progress to Fix committed
  • % Done changed from 88 to 100

Applied in changeset commit:86a2af348e8cb86fbc8c702ab72f4dd54713f29d.

#7 Updated by anonym 2015-10-26 13:04:50

  • QA Check changed from Ready for QA to Pass

#8 Updated by anonym 2015-10-26 16:03:47

  • Assignee deleted (anonym)

#9 Updated by anonym 2015-11-03 11:30:12

  • Status changed from Fix committed to Resolved