Feature #10310

Assistant: Write "Clone" scenario

Added by sajolida 2015-09-30 09:49:25 . Updated 2015-11-01 08:26:13 .

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

100%

Feature Branch:
web/10310-clone
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Installation Assistant
Deliverable for:

Description


Subtasks

Feature #9444: Assistant: Explain how to verify that the source USB is up-to-date Resolved

0


History

#1 Updated by sajolida 2015-10-10 10:57:55

  • Assignee changed from sajolida to tchou

This is ready for review as well.

I based my branch on web/10309-linux but that shouldn’t make your review more complicated. To look at the changes implied by this particular branch you can do:

git log -p origin/web/10309-linux-usb...origin/web/10310-clone

You’ll probably notice that a few commits in there are not directly related to the work at stake but I spot them while working on this. I made only changes to the phrasing and separated them clearly so you can check them one by one. If you disagree with any of them, please tell me. They are bf76364, b989ff8, 0ea9f20, f2c4847, and a33586d.

Slightly unrelated as well, but please answer here quickly if you think that’s not subjet to more debates. I’m also wondering whether we should add a “Tails” label to https://git-tails.immerda.ch/tails/plain/wiki/src/install/inc/infography/create-persistence.png?h=web/10310-clone which is happening in Tails as well as https://git-tails.immerda.ch/tails/plain/wiki/src/install/inc/infography/plug-second-usb.png?h=web/10310-clone.

Also note that I didn’t adapt the troubleshooting sections to the case of using a Tails DVD to bootstrap. Tell me if you think that’s needed.

#2 Updated by sajolida 2015-10-10 10:58:24

  • QA Check set to Ready for QA
  • Feature Branch set to web/10310-clone

#4 Updated by tchou 2015-10-13 14:44:17

  • Assignee changed from tchou to sajolida

I think it’s OK as it is. We allways have text explaination with the icons.

Ready for “resolved”.

#5 Updated by sajolida 2015-10-14 06:41:31

  • QA Check changed from Ready for QA to Dev Needed

If tchou is happy with ada0e11, then I should apply similar tricks everywhere and work on this branch again before merging.

#6 Updated by sajolida 2015-10-23 08:05:13

  • Assignee changed from sajolida to tchou
  • QA Check changed from Dev Needed to Ready for QA

Done. In the end I cherry-picked the more complex solution that I developped while working on the Mac scenarios. Maybe I’m creating a Git monster here, but we’ll see and I’ll pay the consequences.

So could you review again this particular part (which will be the same as in web/10313-mac-usb one I’ll push it). That’s commit 225c1a2.

Then I’ll do the merge.

#7 Updated by tchou 2015-10-27 04:40:58

Same comment than elsewhere, but it’s OK. (and I just remember the git show command, it’s handy :)

#8 Updated by tchou 2015-10-27 04:41:35

  • Assignee changed from tchou to sajolida
  • QA Check deleted (Ready for QA)

#9 Updated by sajolida 2015-10-27 10:18:44

Waiting for the resolution of Feature #10313#note-6 then.

#10 Updated by sajolida 2015-10-27 10:38:07

  • QA Check set to Pass

#11 Updated by sajolida 2015-10-28 08:36:22

  • Assignee deleted (sajolida)
  • QA Check deleted (Pass)

Merged as well now that Feature #10313 is merged.

#12 Updated by sajolida 2015-11-01 08:18:46

  • Status changed from Confirmed to Resolved