Feature #16991
Cognitive walkthrough of automatic and manual upgrades
0%
Description
I never use Tails Upgrader myself and we don’t have RMs resources to do a usability testing of the whole process, so I’ll do a cognitive walkthrough of the entire processes.
Upgrades are still the most frequent complain when interviewing users, I’m afraid that Feature #15281 will actually make things a bit more painful for people with poor Internet connection (eg. most of the Global South), and there might be other low-hanging fruits elsewhere (doc, phrasing, feedback, etc.).
Subtasks
Related issues
Related to Tails - |
Resolved | 2016-01-08 | |
Related to Tails - |
Resolved | ||
Blocks Tails - |
Resolved | ||
Blocks Tails - Feature #15288: Document tricks for power users vs. bigger downloads for automatic upgrade | Confirmed | 2018-02-05 |
History
#1 Updated by sajolida 2019-08-22 15:14:50
- blocks
Feature #16688: Core work 2019Q3 → 2019Q4: User experience added
#2 Updated by sajolida 2019-09-18 19:24:38
- related to
Feature #10885: Better integrate new upgrade scenarios with upgrade documentation added
#3 Updated by sajolida 2019-10-18 02:35:01
- related to
Feature #17151: Point Tails Upgrader to /doc/upgrade added
#4 Updated by sajolida 2019-10-18 02:36:04
I did the one for manual upgrades. See Feature #10885, Feature #17151, Bug #17069, and Bug #17068.
#5 Updated by sajolida 2019-11-27 17:12:40
- Target version set to Tails_4.1
I’ll do this when upgrading myself from 4.0 to 4.1.
#6 Updated by sajolida 2019-11-27 17:12:55
- Target version changed from Tails_4.1 to Tails_4.2
#7 Updated by sajolida 2019-11-27 17:13:10
- blocks Feature #15288: Document tricks for power users vs. bigger downloads for automatic upgrade added
#8 Updated by sajolida 2019-12-04 12:26:37
- Status changed from Confirmed to Resolved
I did the one for automatic upgrades when upgrading my machine from 4.0 to 4.1: Feature #17314, Feature #17312, Feature #17313, Feature #17310, Feature #7878#note-9, Feature #6502.