Feature #11232

Evaluate changes brought by Jessie 8.4 ahead of its release

Added by anonym 2016-03-14 13:11:31 . Updated 2016-04-26 09:14:01 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2016-03-14
Due date:
2016-04-02
% Done:

100%

Feature Branch:
Type of work:
Wait
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

The next point release for Jessie, 8.4, is scheduled for 2016-04-02. So we should enable the jessie-proposed-updates APT repository in devel (but no stable in case there’s a need for an emergency release) as soon as possible to catch any issues early.

Tails 2.3 is scheduled for 2016-04-19 so Jessie 8.4 will be released by then and we should not release it with jessie-proposed-updates enabled — it will only be temporarily enable in devel in between releases.


Subtasks


History

#1 Updated by anonym 2016-03-14 13:13:41

  • Assignee set to intrigeri
  • QA Check set to Info Needed

intrigedi, do you feel the plan in the description is correct? Otherwise, feel free to refine it.

I intend to deal with this, so please reassign to me when done.

#2 Updated by intrigeri 2016-03-14 13:31:36

  • Assignee changed from intrigeri to anonym
  • QA Check changed from Info Needed to Dev Needed

> intrigedi, do you feel the plan in the description is correct?

Yes!

#3 Updated by anonym 2016-03-14 15:10:24

  • Due date set to 2016-04-02
  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 30
  • Type of work changed from Code to Wait

I’ve pushed commit:07b59189b78637025fb49634a2e3cd79da5e555d for this. I’ve scheduled the revert in my personal TODO.

#4 Updated by anonym 2016-04-11 03:40:16

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 30 to 100
  • QA Check changed from Dev Needed to Pass

Reverted in commit:cae496a73d55588db73634ba1a0ebfac9c7e3714.

#5 Updated by anonym 2016-04-26 09:14:01

  • Status changed from Fix committed to Resolved