Tails

#1 Updated by intrigeri 2014-07-24 16:24:47

I think we have several different minor problems here, that, once combined together, indeed can create much confusion.

> Users of Tails 1.0.1 actually get an upgrade notification, from the IUK, pointing to
> this page https://tails.boum.org/doc/first_steps/upgrade/#manual
> First, this is not clear enough that translations of this chapter exist, as the links
> to switch languages only appear at the top of the page.

This is a bug in the German and Portuguese translations of the automatic upgrade software (tails-iuk). The French translation rightfully points to the French translation of this page. Granted, we don’t document anywhere how to translate such URLs. I think this should be reported to the German and Portuguese translation teams on Transifex, or last translators (as found in the corresponding PO files). pilop, do you want to do that, by chance?

> Moreover, users ask if they should use those instructions or https://tails.boum.org/news/version_1.1/#index5h1

Understood. IMO, the upgrade documentation should point to the latest version of the release notes, and strongly recommend reading it. Note that the very same dialog window, in tails-iuk, that points to that documentation also points to the release notes, but it now seems clear to me that it’s not enough.

#2 Updated by sycamoreone 2014-07-24 19:31:28

intrigeri wrote:
> This is a bug in the German and Portuguese translations of the automatic upgrade software (tails-iuk). The French translation rightfully points to the French translation of this page. Granted, we don’t document anywhere how to translate such URLs. I think this should be reported to the German and Portuguese translation teams on Transifex, or last translators (as found in the corresponding PO files). pilop, do you want to do that, by chance?
>
I think I can take care of the German translation.

#3 Updated by sycamoreone 2014-07-24 19:53:13

sycamoreone wrote:
> I think I can take care of the German translation.

Now, I think that I fixed this in Transifex,
but this is the first time I am using Transifex,
and I don’t see how to verify that I did the right
thing.

#4 Updated by sycamoreone 2014-07-24 20:20:00

The German fix made it to the translations git-repository.

#5 Updated by sycamoreone 2014-07-24 20:36:15

pilop wrote:
> First, this is not clear enough that translations of this chapter exist, as the links to switch languages only appear at the top of the page.

Actually a German translation of these pages doesn’t exist (but a French and Portuguese). Next project.

#6 Updated by intrigeri 2014-07-24 21:23:36

Pushed a quick’n’dirty workaround (commit bbbfd42) to avoid seeing too many more users fall into this trap. There’s already been way too many.

#8 Updated by intrigeri 2014-07-24 22:33:14

> Actually a German translation of these pages doesn’t exist (but a French and Portuguese).

Ha. Indeed, even pointing users to the right URL wouldn’t do much good (yet), then :]

> Next project.

\o/

#9 Updated by sycamoreone 2014-07-25 08:40:09

intrigeri wrote:
> Pushed a quick’n’dirty workaround (commit bbbfd42) to avoid seeing too many more users fall into this trap. There’s already been way too many.

Is there some ikiwiki magic (e.g. by defining a shortcut?)
we could use to make this link always point to the newest
release notes?

If there is no easy way I will at least create a ticket for this;
hard coding to version_1.1 will make problems some day.

#11 Updated by intrigeri 2014-07-25 10:02:22

> Is there some ikiwiki magic (e.g. by defining a shortcut?)
> we could use to make this link always point to the newest
> release notes?

Inlining inc/stable_i386_version might work. We’re doing that on the sidebar and download page already, I think.

Note that I also updated the release process doc so that the RM thinks of updating this link. My workaround was quick’n’dirty, but not that crazy :)

#12 Updated by sajolida 2014-07-25 18:02:02

>> > Is there some ikiwiki magic (e.g. by defining a shortcut?)
>> > we could use to make this link always point to the newest
>> > release notes?
> Inlining inc/stable_i386_version might work. We’re doing that on the sidebar and download page already, I think.

If I remember correctly, the problem with those inlines is that a new
line is added after each one of them. So it is not possible to have
“1.1” in one file and to reuse it everywhere we need.

That’s why we had to create different inline files for each piece of
information: the ISO file, the torrent file, etc. We would have to
create a new inline file for the release notes :(

ikiwiki is a bit limited sometimes…

#13 Updated by intrigeri 2014-07-26 07:52:17

> That’s why we had to create different inline files for each piece of
> information: the ISO file, the torrent file, etc. We would have to
> create a new inline file for the release notes :(

Yeah, but in practice that’s no big deal. See the “version number” section on the release process doc. Adding a 3rd echo command-line won’t change the amount of work the release manager has to do: copying’n’pasting 2 lines or 3 at a time doesn’t make much of a difference.

#14 Updated by sajolida 2014-07-26 08:53:06

> Yeah, but in practice that’s no big deal. See the “version number”
> section on the release process doc. Adding a 3rd echo command-line
> won’t change the amount of work the release manager has to do:
> copying’n’pasting 2 lines or 3 at a time doesn’t make much of a
> difference.

I’m glad to know that you validate this proposal. So I created Feature #7665.

Can we mark this ticket as resolved then?