Bug #10624

Rethink how we present limitations on Mac

Added by sajolida 2015-11-24 02:08:48 . Updated 2015-12-17 04:17:31 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Installation
Target version:
Start date:
2015-11-24
Due date:
% Done:

0%

Feature Branch:
web/10624-mac-limitations
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Installation Assistant
Deliverable for:

Description

  • Restructure introduction in router not to mention “full-feature” and “minimal” [51] [52] [53]
  • Clarify properties of minimal and full-feature whenever needed [52] [53]

Subtasks


History

#1 Updated by sajolida 2015-11-24 02:45:59

#2 Updated by sajolida 2015-12-09 08:00:59

  • Assignee changed from sajolida to tchou
  • QA Check set to Ready for QA
  • Feature Branch set to web/10624-mac-limitations

Done.

I think that the second point (Clarify properties of minimal and full-feature whenever needed) has already been dealt with in 88a2e5d.

#3 Updated by tchou 2015-12-12 03:40:51

  • Assignee changed from tchou to sajolida

I feel that Tails with <strong>limited features</strong> is a bit too evasive. It can be understood like “I wont’s have this nice to have thing but it can still be OK”. I would suggest Tails with <strong>missing core features</strong>, because Tails will be OK only maximum for 6 weeks.

#4 Updated by sajolida 2015-12-17 04:17:17

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:a6570661f17645623f449fef76db6a1bf16a8828.

#5 Updated by sajolida 2015-12-17 04:17:31

  • Assignee deleted (sajolida)
  • % Done changed from 100 to 0
  • QA Check deleted (Ready for QA)

Thanks for the suggestion. I did that (almost) in fb66007.