Feature #15427

Drop the exceptional manual upgrade steps from 3.2, 3.3, 3.4 and 3.5

Added by intrigeri 2018-03-16 23:01:06 . Updated 2018-06-25 18:40:20 .

Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:
End-user documentation

Affected tool:
Deliverable for:



Related issues

Related to Tails - Feature #15416: Document how to manually upgrade to 3.6 and 3.6.1 for non-English users Resolved 2018-03-16
Blocks Tails - Feature #15411: Core work 2018Q2 → 2018Q3: Technical writing Resolved 2018-03-14


#1 Updated by intrigeri 2018-03-16 23:02:38

  • related to Feature #15416: Document how to manually upgrade to 3.6 and 3.6.1 for non-English users added

#2 Updated by sajolida 2018-05-28 14:08:14

  • blocks Feature #15411: Core work 2018Q2 → 2018Q3: Technical writing added

#3 Updated by sajolida 2018-05-31 15:50:28

  • Assignee changed from sajolida to cbrownstein
  • QA Check set to Ready for QA
  • Feature Branch set to doc/15427-drop-extra-manual-upgrade-steps

Cody: Please have a look!

#4 Updated by sajolida 2018-05-31 15:51:14

  • Status changed from Confirmed to In Progress

#5 Updated by cbrownstein 2018-06-17 07:37:46

  • Assignee changed from cbrownstein to sajolida

While reviewing your branch I noticed that the drop-down list is titled “Target Device” when it should be “Target USB stick.” I’ve fixed that in my branch. Otherwise, looks good!


#6 Updated by sajolida 2018-06-25 16:03:23

  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)
  • QA Check deleted (Ready for QA)

Cool! Thanks for the careful review! I’ll merge this into stable so it’s live when 3.8 is released tomorrow.

#7 Updated by intrigeri 2018-06-25 16:43:13

Dear sajolida, FYI pushing to stable in the middle of the release process messes things up (currently it breaks the build from the stable branch and thus makes it harder to run the test suite on the 3.8 tag). So to fix that without losing your work I have:

  1. merged into web/release-3.8 what you had pushed to stable
  2. forced-push the previous, correct state to stable

If you need to merge doc changes during the release process, please merge into the web/release-$VERSION branch: it’ll be published at the same time as the release. Same for the release notes etc. :)

#8 Updated by sajolida 2018-06-25 17:35:53

Oops, I thought about that but didn’t check the release process to see if it was fine. I should have checked with you on XMPP.

Sorry for the trouble!!!

#9 Updated by intrigeri 2018-06-25 18:40:20

> Sorry for the trouble!!!

No worries, I think it’s the first time our merge / release schedules conflict, and TBH “don’t touch the release branch during the release process if you’re not the IM” is not documented anywhere.