Feature #7740

Remove TrueCrypt

Added by intrigeri 2014-08-04 09:57:44 . Updated 2014-12-04 16:21:42 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_1.2.2
Start date:
2014-08-04
Due date:
% Done:

100%

Feature Branch:
feature/7740-remove-truecrypt
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Once we’ll have shipped the updated TrueCrypt wrapper (Feature #7739) and a documented (Feature #6052) alternative to TrueCrypt (Feature #5932) for a Tails release or two, we can remove TrueCrypt, finally.

Subtasks

Related issues

Blocked by Tails - Feature #7739: Update the TrueCrypt wrapper to make the migration path clearer Resolved 2014-08-04
Blocked by Tails - Feature #6052: Document alternative to TrueCrypt Resolved
Blocked by Tails - Feature #5932: Implement alternative to TrueCrypt Resolved 2014-08-04

History

#1 Updated by intrigeri 2014-08-04 09:58:08

  • blocked by Feature #7739: Update the TrueCrypt wrapper to make the migration path clearer added

#2 Updated by intrigeri 2014-08-04 09:58:22

  • blocked by Feature #6052: Document alternative to TrueCrypt added

#3 Updated by intrigeri 2014-08-04 09:58:32

  • blocked by Feature #5932: Implement alternative to TrueCrypt added

#4 Updated by intrigeri 2014-08-13 13:42:37

  • Status changed from Confirmed to In Progress
  • Assignee set to intrigeri
  • % Done changed from 0 to 10
  • Feature Branch set to feature/7740-remove-truecrypt

Done: removing TC support, adjusting all references to the doc but the main page about TrueCrypt.

Left to do: update the main doc page about TrueCrypt.

#5 Updated by intrigeri 2014-09-25 18:10:56

  • Target version changed from Tails_1.3 to Tails_1.2.1

#6 Updated by intrigeri 2014-09-25 18:17:31

  • Assignee changed from intrigeri to sajolida
  • % Done changed from 10 to 30
  • QA Check set to Ready for QA

sajolida, please review the doc changes brought in this branch, and once we’re happy with it, reassign to me. Then, I’ll do the final testing of the code changes, and will ask for a review’n’merge.

#7 Updated by intrigeri 2014-10-17 05:44:23

  • Assignee changed from sajolida to intrigeri
  • % Done changed from 30 to 40
  • QA Check deleted (Ready for QA)

Doc review and improvement was done.

#8 Updated by intrigeri 2014-10-17 14:27:27

  • Assignee deleted (intrigeri)
  • % Done changed from 40 to 50
  • QA Check set to Ready for QA

#9 Updated by anonym 2014-11-25 15:16:39

  • Assignee set to anonym

#10 Updated by anonym 2014-11-30 22:39:48

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

#11 Updated by BitingBird 2014-12-03 19:41:49

  • Status changed from Fix committed to Resolved

#12 Updated by sajolida 2014-12-04 12:07:53

  • Status changed from Resolved to Confirmed
  • Assignee set to anonym
  • Target version changed from Tails_1.2.1 to Tails_1.2.2
  • QA Check changed from Pass to Ready for QA
  • commit:5a7a98b
  • commit:0f41c36

#13 Updated by intrigeri 2014-12-04 16:21:42

  • Status changed from Confirmed to Resolved
  • Assignee deleted (anonym)
  • QA Check changed from Ready for QA to Pass

Merged. May I ask that we refrain from reopening tickets related to branches that were already merged, in general? Thanks :)