Tails

#1 Updated by intrigeri 2017-12-06 14:50:27

• related to Bug #15018: Decide if we do a Tails 3.3.1 emergency release added

#2 Updated by intrigeri 2017-12-06 14:50:29

• blocks Feature #13244: Core work 2017Q4: Foundations Team added

#3 Updated by intrigeri 2017-12-08 18:09:26

• Status changed from Confirmed to In Progress
• % Done changed from 0 to 10
• Feature Branch set to bugfix/15019-tor-0.3.1.9

Post-merge action needed

If this gets merged for Tails 3.5, we will need to bump the expiration date of this newer APT snapshot so it matches the expiration date of the debian one.

#4 Updated by intrigeri 2017-12-09 07:43:56

• % Done changed from 10 to 20

First (partial) test results on lizard look good, started a full run on my local Jenkins.

#5 Updated by intrigeri 2017-12-09 13:52:55

• Assignee changed from intrigeri to anonym
• % Done changed from 20 to 50
• QA Check set to Ready for QA

Only unrelated failures in my full test suite run.

Beware! see “Post-merge action needed” above.

#6 Updated by anonym 2017-12-14 12:54:37

• 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

intrigeri wrote:
> h2. Post-merge action needed
>
> If this gets merged for Tails 3.5, we will need to bump the expiration date of this newer APT snapshot so it matches the expiration date of the debian one.

Merged and bumped! Details: Feature #14999#note-14

#7 Updated by intrigeri 2018-01-04 18:26:39

• Target version changed from Tails_3.5 to Tails_3.4

#8 Updated by anonym 2018-01-09 20:52:39

• Status changed from Fix committed to Resolved