Bug #12365
Upgrade automatic and manual upgrade screenshots
Start date:
2017-03-18
Due date:
% Done:
0%
Description
Once 3.1 is out:
- We should upgrade the automatic upgrade screenshot in /doc/first_steps/upgrade.
- We could add another one for manual upgrade so that both contexts are clarified.
But let’s not bother doing that before 3.0 because it would be too painful to be worth it.
Subtasks
Related issues
|
Related to Tails - |
Resolved | 2016-08-29 | |
|
Related to Tails - |
Resolved | 2017-04-29 | |
|
Related to Tails - |
Resolved | 2017-03-20 | |
|
Blocks Tails - |
Resolved | 2017-07-05 |
History
#1 Updated by intrigeri 2017-03-18 11:33:41
> But let’s not bother doing that before 3.0 because it would be too painful to be worth it.
FWIW we have automated tests for this feature, so one option would be to grab the relevant frame in the recorded video.
#2 Updated by sajolida 2017-03-18 11:34:46
- related to
Bug #11742: Update doc screenshots for 3.0 added
#3 Updated by Anonymous 2017-06-30 13:08:49
- related to
Feature #12492: Instruct people with a version older than n-2 to do manual upgrade in /doc/upgrade/error/check added
#4 Updated by Anonymous 2017-06-30 13:09:02
- related to
Bug #12392: Correct documentation regarding 'Check for updates' added
#5 Updated by spriver 2017-08-29 11:00:48
- Assignee set to spriver
#6 Updated by spriver 2017-09-03 09:22:57
- Status changed from Confirmed to In Progress
- Assignee changed from spriver to sajolida
- QA Check set to Ready for QA
- Feature Branch set to spriver:web/12365-update-upgrader-screenshots
I updated the current screenshot proposing to do a automatic upgrade and added one which is proposing a manual upgrade (and adapted the doc accordingly to it).
#7 Updated by sajolida 2017-09-05 08:17:19
- blocks
Feature #13423: Core work 2017Q3: Technical writing added
#8 Updated by sajolida 2017-09-17 17:56:51
- Status changed from In Progress to Resolved
- Assignee deleted (
sajolida) - QA Check deleted (
Ready for QA)
Cool, I’m merging!