Project

General

Profile

Feature #12163

Announce in advance that 3.0 will be 64-bit only

Added by intrigeri 10 months ago. Updated 9 months ago.

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

100%

QA Check:
Pass
Feature Branch:
Type of work:
Communicate
Blueprint:
Easy:
Affected tool:

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 onlyResolvedintrigeri

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


Related issues

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

History

#1 Updated by Anonymous 10 months ago

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 10 months ago

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

#3 Updated by intrigeri 10 months ago

  • Status changed from Confirmed to In Progress

#4 Updated by intrigeri 10 months ago

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

#5 Updated by anonym 9 months ago

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

#6 Updated by intrigeri 9 months ago

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

#7 Updated by anonym 9 months ago

  • Assignee changed from anonym to intrigeri

#8 Updated by intrigeri 9 months ago

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

#9 Updated by anonym 9 months ago

  • Status changed from Fix committed to Resolved

Also available in: Atom PDF