Feature #12163

Announce in advance that 3.0 will be 64-bit only

Added by intrigeri 2017-01-22 08:50:32 . Updated 2017-03-09 13:56:50 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Hardware support
Target version:
Tails_2.11
Start date:
2017-01-30
Due date:
% Done:

100%

Feature Branch:
Type of work:
Communicate
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

We should communicate this early enough to our users, so that they can plan any needed hardware upgrade accordingly. I’d like to do during the 2017-01 sprint. I’ll draft something; it would be awesome if sajolida could review and improve it, but not a strict requirement.

Subtasks

Feature #12192: Blog post to announce that 3.0 will be 64-bit only Resolved intrigeri

100
Feature #12193: Notify the user when their 32-bit computer won't work with Tails 3.0 Resolved

100

Related issues

Related to Tails - Feature #8183: Ship a 64-bit (x86_64) instead of 32-bit userspace Resolved 2016-10-11

History

#1 Updated by Anonymous 2017-01-24 23:32:57

i am not sure this is a good idea will 32bit support dropped entirely?
there is a lot of capable hardware without 64bit support like the type which runs libreboot

how is RMS gonna boot into tails now? :-(

#2 Updated by intrigeri 2017-01-30 14:46:17

  • related to Feature #8183: Ship a 64-bit (x86_64) instead of 32-bit userspace added

#3 Updated by intrigeri 2017-01-30 16:50:29

  • Status changed from Confirmed to In Progress

#4 Updated by intrigeri 2017-02-01 12:25:05

  • Assignee changed from intrigeri to anonym
  • QA Check set to Ready for QA

#5 Updated by anonym 2017-02-17 17:07:07

  • Assignee changed from anonym to intrigeri
  • QA Check changed from Ready for QA to Dev Needed

#6 Updated by intrigeri 2017-03-02 10:09:43

  • Assignee changed from intrigeri to anonym
  • QA Check changed from Dev Needed to Ready for QA

#7 Updated by anonym 2017-03-05 14:04:20

  • Assignee changed from anonym to intrigeri

#8 Updated by intrigeri 2017-03-05 16:03:34

  • Status changed from In Progress to Fix committed
  • Assignee deleted (intrigeri)
  • QA Check changed from Ready for QA to Pass

#9 Updated by anonym 2017-03-09 13:56:50

  • Status changed from Fix committed to Resolved