Tails

#1 Updated by Anonymous 2015-07-03 06:34:19

• Assignee deleted (None)

#2 Updated by BitingBird 2015-07-03 08:56:46

• Category set to Installation
• Affected tool set to Installer

#3 Updated by Anonymous 2015-07-04 02:12:17

• % Done changed from 0 to 10
• Feature Branch set to 451f:doc/installer_wording

#4 Updated by Anonymous 2015-07-04 02:14:14

• Status changed from Confirmed to In Progress
• Assignee set to intrigeri
• QA Check set to Ready for QA

#5 Updated by intrigeri 2015-07-04 02:48:32

• Target version set to Tails_1.5

#6 Updated by intrigeri 2015-07-04 09:47:15

• blocks #8538 added

#7 Updated by intrigeri 2015-07-04 09:51:12

• Assignee deleted (intrigeri)
• % Done changed from 10 to 100
• QA Check changed from Ready for QA to Pass

Looks good, and it seems to not be directly affected by the terminology discussion that was restarted on Feature #8866 and on -ux@. Can’t merge it yet though, since we first need to decide something wrt. the wording so that the branch for Feature #9672 can be adjusted, and then both branches can be merged at the same time => please reassign to me once we’re there.

#8 Updated by Anonymous 2015-08-04 07:42:31

• Target version changed from Tails_1.5 to Tails_1.6

#9 Updated by intrigeri 2015-08-19 08:31:25

• % Done changed from 100 to 80
• QA Check deleted (Pass)

We should check if this is affected by the last wording decision.

#13 Updated by Anonymous 2015-08-21 01:29:57

• Assignee set to sajolida
• QA Check set to Ready for QA

sajolida wrote:
> Fixed on /contribute/how/translate/team/de then.

thanks, i was not aware that this was broken.

> So that’s the end-user doc. I really don’t mind you updating it but I have time allocated for that myself and will go through the full doc anyway before we release it. So you can assign this ticket to me if you prefer for review or anything.

I updated it a bit, but I would indeed appreciate that you verify and correct what I did there :)
Reassigning the ticket to you for review.

> By the way, will the version of Tails Installer with the new wording be updated in Tails 1.6?

I will verify this.

#15 Updated by sajolida 2015-09-09 08:57:41

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

I built up on your branch which updated the documentation to the new wording and availability of Tails Installer in Debian and Ubuntu.

Still, I don’t think we could yet document Tails Installer outside of Debian in 1.6. What is the ETA before having it in backports? If the new wording ends up in Tails before Tails Installer ends up in Debian backports, then we should split the changes introduced in this branch to only mention the change of wording in Tails Installer inside Tails.

It seems like we both overlooked this while working on this branch and broaden its scope to include Tails Installer outside of Tails. Tell what are your ETAs and then I’ll propose something to fix this.

#19 Updated by Anonymous 2015-09-22 15:24:05

• Target version changed from Tails_1.6 to Tails_1.7

#20 Updated by intrigeri 2015-10-02 15:51:31

• Assignee set to sajolida
• % Done changed from 80 to 0
• QA Check changed from Info Needed to Dev Needed

Sorry for the delay.

sajolida wrote:
> If the new wording ends up in Tails before Tails Installer ends up in Debian backports, then we should split the changes introduced in this branch to only mention the change of wording in Tails Installer inside Tails.

I’d rather not make the rewording (that’s almost completed and should go in 1.7, which will be frozen in ~3 weeks, and is our last major release before the end of the year) depend on the timing on the Debian side (which is harder to predict) => let’s deal with these two problems separately. The one that’s out of the scope of this ticket is tracked by Feature #8563.

> Tell what are your ETAs and then I’ll propose something to fix this.

We’re working hard to do an initial upload to Debian experimental or sid this month, so that the package can hopefully clear the NEW queue while we fix the last remaining bits before we let it migrate to testing and upload to jessie-backports. (If this timing is problematic for reasons that are out of the scope of this ticket, let’s discuss it elsewhere. Thanks!)

Please update the topic branch field so that it’s clear where the latest version of your work lives, by the way :)

#22 Updated by intrigeri 2015-10-03 05:47:46

• blocks Feature #9672: Rework wording of Tails installer in Wheezy added

#27 Updated by sajolida 2015-10-13 06:14:18

• Assignee changed from sajolida to anonym
• QA Check changed from Dev Needed to Ready for QA
• Feature Branch changed from 451f:doc/installer_wording to feature/9672-rework-installer-wording-on-wheezy

So I cherry-picked the two commits from u that were directly related to the change of wording on the interface into feature/9672-rework-installer-wording-on-wheezy and I think that’s it for the time being.

What took me the more time on this was to actually figure out what was expected on this ticket. Now it looks a bit silly :)

anonym, is it enough to unblock you?

#28 Updated by anonym 2015-10-13 18:47:05

• Status changed from In Progress to Fix committed
• Assignee deleted (anonym)
• % Done changed from 0 to 100
• QA Check changed from Ready for QA to Pass

sajolida wrote:
> So I cherry-picked the two commits from u that were directly related to the change of wording on the interface into feature/9672-rework-installer-wording-on-wheezy and I think that’s it for the time being.
>
> What took me the more time on this was to actually figure out what was expected on this ticket. Now it looks a bit silly :)
>
> anonym, is it enough to unblock you?

It did, thanks! I’m marking this one Fix Committed too given that you set the same feature branch, and assigned it as Ready for QA to me. Please undo this if I was assuming too much!

#29 Updated by anonym 2015-11-03 11:30:53

• Status changed from Fix committed to Resolved