Tails

#1 Updated by intrigeri 2013-07-19 02:43:38

• Priority changed from Normal to High

#2 Updated by BitingBird 2014-06-20 13:24:29

• Subject changed from fix re-test in secure Icedove autoconfig wizard to Fix re-test in secure Icedove autoconfig wizard
• Starter set to No

#3 Updated by sajolida 2014-07-10 20:23:37

• Priority changed from High to Normal

#4 Updated by intrigeri 2014-08-12 13:44:32

• Category set to 212

#5 Updated by BitingBird 2015-01-04 02:53:18

• related to Feature #6158: Fix secure Icedove autoconfig wizard in Tails added

#6 Updated by intrigeri 2015-01-04 12:46:14

• related to deleted (Feature #6158: Fix secure Icedove autoconfig wizard in Tails)

#7 Updated by intrigeri 2015-05-29 12:33:14

• Assignee set to kytv
• Target version set to 246

#8 Updated by intrigeri 2015-05-29 12:33:25

• blocks #8668 added

#9 Updated by sajolida 2015-11-27 04:45:21

• Target version changed from 246 to Tails_2.0

#10 Updated by Anonymous 2015-12-22 06:57:05

• Target version changed from Tails_2.0 to Tails_2.2

#11 Updated by Anonymous 2015-12-22 07:06:44

• Target version changed from Tails_2.2 to Tails_2.0

This should actually be done for the release of 2.0 (without the need to be merged into 2.0) so that we can have a working PoC for 2.2.

#12 Updated by Anonymous 2015-12-30 04:40:15

• related to Feature #6369: Build Debian packages of Icedove 38 with our patches / create proper branch situation added

#13 Updated by kytv 2016-01-06 14:29:05

• Target version changed from Tails_2.0 to Tails_2.2

#14 Updated by intrigeri 2016-01-06 16:20:01

• Target version changed from Tails_2.2 to Tails_2.0

I think I’ve mislead you somewhat early today, when I asked you to update your Icedove tickets. Sorry about that!

According to the timeline proposed on https://mailman.boum.org/pipermail/tails-icedove/2015-December/000108.html, we want a working PoC of the wizard ready during the 2.0 release cycle, so I think this ticket needs to stay on the 2.0 board for now.

Another option, which is rather what I was implicitly suggesting, would be to make it explicit (by creating new tickets) that the PoC is for 2.0, and that the goal is to have it merged for 2.2.

#15 Updated by Anonymous 2016-02-05 16:47:07

• Target version changed from Tails_2.0 to Tails_2.2

#16 Updated by Anonymous 2016-02-24 11:23:49

• Target version changed from Tails_2.2 to Tails_2.3

#18 Updated by anonym 2016-03-10 12:57:42

• Assignee changed from kytv to anonym

#19 Updated by anonym 2016-04-20 10:56:44

• Target version changed from Tails_2.3 to Tails_2.4

#20 Updated by intrigeri 2016-05-10 04:45:02

• blocked by deleted (#8668)

#21 Updated by intrigeri 2016-05-10 04:46:38

• Status changed from Confirmed to In Progress

My understanding is that this has been fixed, and will be shipped to users as part of the branch for Feature #6154. If I’m correct, then please close this ticket as resolved (it’s a part of Feature #6154, and it’s not a bug that affects any released version of Tails, so no need to go through “Fix committed” :)

#22 Updated by anonym 2016-05-10 06:13:17

• Status changed from In Progress to Resolved
• Assignee deleted (anonym)

#23 Updated by intrigeri 2016-05-24 21:28:02

• % Done changed from 0 to 100