summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Translated using Weblate (French)HEADmasterxin32 hours1-2/+7
| | | | Currently translated at 97.5% (118 of 121 strings)
* Translated using Weblate (French)xin2 days1-7/+3
| | | | | | | Currently translated at 100.0% (9 of 9 strings) Translation: Tails/wiki/src/home/testing.*.po Translate-URL: http://translate.tails.boum.org/projects/tails/wikisrchometestingpo/fr/
* Weblate commitxin2 days1-27/+20
|
* Add missing 4.0~rc1 artifact.intrigeri3 days1-0/+1689
|
* Revert spam.intrigeri3 days1-2/+2
|
* This reverts commit 1b55e0fb3db353802aea20b13edc8024ff1aacb5127.0.0.13 days1-1/+1
|
* This reverts commit d987b554814e4dda4cd5ac357b00f203cdc5d012127.0.0.13 days1-1/+1
|
* Update ticket number: it was decided not to do this as part of #15086, but ↵intrigeri3 days1-1/+1
| | | | as a follow-up task.
* merge with main git using update_weblate_git.py.Tails translators3 days23-623/+669
|\ | | | | | | | | | | | | | | | | | | | | wiki/src/contribute.ar.po: updating as wiki/src/contribute.de.po has changed. wiki/src/contribute.ca.po: updating as wiki/src/contribute.de.po has changed. wiki/src/contribute.id.po: updating as wiki/src/contribute.de.po has changed. wiki/src/contribute.pl.po: updating as wiki/src/contribute.de.po has changed. wiki/src/contribute.ru.po: updating as wiki/src/contribute.de.po has changed. wiki/src/contribute.sr_Latn.po: updating as wiki/src/contribute.de.po has changed. wiki/src/contribute.tr.po: updating as wiki/src/contribute.de.po has changed. wiki/src/contribute.zh.po: updating as wiki/src/contribute.de.po has changed. wiki/src/contribute.zh_TW.po: updating as wiki/src/contribute.de.po has changed.
| * updated PO filesIkiWiki3 days6-7/+30
| |
| * Move translation platform design doc under contribute/design (refs: #15086).intrigeri3 days3-486/+497
| | | | | | | | | | | | | | | | | | | | | | | | | | While doing so: - implement some structure improvements that we discussed on the ticket - various small polishing And accordingly: - adjust internal links - adjust backlinks
| * Move translation platform specs to a subpage of the upcoming design doc ↵intrigeri3 days2-53/+52
| | | | | | | | (refs: #15086).
| * Move translation platform ops doc under its (future) role page (refs: #15086).intrigeri3 days5-68/+72
|/
* Switch RMs for 4.1.intrigeri4 days1-1/+1
|
* Monthly report: take the 2019-12 one.intrigeri4 days1-1/+1
|
* Revert spam.intrigeri4 days1-1/+1
| | | | This reverts commit 7a4c9da771a8f7d6a8365d988e3418bda3b1e18b.
* Release schedule: remove dead link.intrigeri4 days1-3/+0
| | | | | | | | | | | | | | | I've tried to find this post and the best I could find is https://lists.autistici.org/message/20120428.185212.f0ff0ca2.en.html, where I advocated in favour of a time-based release schedule, for a variety of reasons. Since then, we've consistently aligned our release schedule with Tor Browser's (and thus, transitively, with Firefox's) in order to let our users down with known security vulnerabilities in the most important app we ship: the web browser. So at this point, the other reasons why one may prefer a time-based release schedule don't matter much anymore.
* Release schedule: make terminology consistent.intrigeri4 days1-1/+1
|
* Release schedule: drop obsolete remaining issue.intrigeri4 days1-5/+0
| | | | | | | | | | | | For year: - We've been running the automated test suite continuously as part of our development process - We go through our manual test suite for every release candidate, because we want folks to be able to rely on it sufficiently for production usage. This also allows us to find bugs ourselves, that volunteer testers may not find.
* Calendar: tentatively schedule post-pwn2own emergency releaseintrigeri4 days1-0/+3
|
* Release schedule: document emergency releases.intrigeri4 days1-0/+7
| | | | | So far they were only mentioned in the "Versioning scheme" section but we did not tell what they were about.
* Release schedule: make theory closer to reality.intrigeri4 days1-3/+4
| | | | | | | | | In practice we've given up on "every second scheduled release is a major one" two years ago. Number of major releases per year: - 2017: 4 - 2018: 2 - 2019: 2
* Release schedule: drop obsolete info.intrigeri4 days1-3/+2
|
* text127.0.0.14 days1-1/+1
| | | | This reverts commit b17fde14d53ce444412d68b6011abd88c11ff7b7
* Remove obsolete detail.intrigeri4 days1-2/+1
| | | | | | Firefox has moved away from the fixed 6-weeks schedule a year ago or so, and it's now moving to 4-weeks, so let's not keep mostly useless info that we don't manage to maintain.
* RM'ing: mention the possibility to import Tor Browser earlier than ↵intrigeri4 days1-1/+3
| | | | pre-release Monday.
* RM'ing: mention the possibility to split changelog writing in several sessions.intrigeri4 days1-0/+21
| | | | | One of our RMs mentioned that doing it all at once is potentially unhealthy. Let's make it explicit that one can start earlier and split this work :)
* Release process: move updating Tor Browser before custom Debian packages.intrigeri4 days1-10/+10
| | | | | | | | Part of updating Tor Browser requires waiting for test suite results, which can take hours. While this is running one can do the next steps. Besides, updating Tor Browser can generally be done in the week-end preceding the release instead of on Monday $morning.
* RM'ing: call for manual testers for Tails vN+1 immediately after releasing ↵intrigeri4 days2-4/+15
| | | | | | | | | | | | | | Tails vN. Rationale: we're operating with a pool of manual testers that's dangerously small, in particular considering we'll switch to a 4-weeks release cadence soon. One potential explanation for this is that we often announce late in the release cycle the date when we'll need testers. Let's try to increase the chances testers can book time for this, by telling them about it earlier. This was discussed by the RM team in the "RMs doing more and more manual tests [Was: 3.16 post-releasem]" thread. The same idea was suggested independently by someone else on tails@.
* Calendar: remove past events.intrigeri4 days1-4/+0
|
* merge with main git using update_weblate_git.py.Tails translators4 days44-7015/+295
|\ | | | | | | | | | | | | | | | | | | | | wiki/src/home/testing.ar.po: updating as wiki/src/home/testing.de.po has changed. wiki/src/home/testing.ca.po: updating as wiki/src/home/testing.de.po has changed. wiki/src/home/testing.id.po: updating as wiki/src/home/testing.de.po has changed. wiki/src/home/testing.pl.po: updating as wiki/src/home/testing.de.po has changed. wiki/src/home/testing.ru.po: updating as wiki/src/home/testing.de.po has changed. wiki/src/home/testing.sr_Latn.po: updating as wiki/src/home/testing.de.po has changed. wiki/src/home/testing.tr.po: updating as wiki/src/home/testing.de.po has changed. wiki/src/home/testing.zh.po: updating as wiki/src/home/testing.de.po has changed. wiki/src/home/testing.zh_TW.po: updating as wiki/src/home/testing.de.po has changed.
| * Merge remote-tracking branch 'origin/web/release-4.0-rc1'intrigeri4 days35-6988/+268
| |\ |/ /
| * Document known issue (refs: #17150)intrigeri4 days1-0/+5
| |
| * Release process: drop obsolete step.intrigeri5 days1-7/+0
| | | | | | | | | | | | This was caused by an ikiwiki bug which we fixed a few months ago. I've been waiting to see if it would reappear, but it did not, so I feel confident removing this check now.
| * Releasing version 4.0~rc1intrigeri5 days8-21/+143
| |
| * Replace 4.0~beta2 Torrents and signatures with 4.0~rc1's.intrigeri5 days10-6934/+14
| |
| * Make wget less verbose.intrigeri5 days1-1/+1
| | | | | | | | | | | | In the environment we're running wget in here, the progress bar is displayed from scratch on a new line for every update, which fills screens of output and may hide useful information.
| * Update upgrade-description files.intrigeri5 days16-25/+103
| |
| * Filter out more mksquasfsh noise.intrigeri5 days1-0/+2
| | | | | | | | | | These files are added to squashfs.sort but they're not present in the tree that mksquashfs compresses, which makes it complain.
* | Manual test suite: exercise our Tier-1 languages instead of an obsolete list.intrigeri4 days1-13/+2
| | | | | | | | | | | | | | That old list comes from the languages that the first version of Tails Greeter offered. Nobody remembers why we picked them. We now have a set of consciously chosen criteria to pick languages that we try to support better than others ⇒ let's focus on those during our manual QA.
* | De-duplicate Tier-1 languages doc.intrigeri4 days1-23/+1
| | | | | | | | | | | | | | | | | | | | I had documented this in our design doc in March (179b33356b487e42a3397d46b17986aac79ac972). A few months later, sajolida document this again elsewhere (ac10f0a3268bab7f7f77a2e596daa3b3748cb7b8) Let's not maintain this info in two different places, especially given it is clearly not obvious how one could/should find the second instance.
* | merge with main git using update_weblate_git.py.Tails translators5 days15-383/+1446
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | wiki/src/install/inc/steps/download.inline.ar.po: updating as wiki/src/install/inc/steps/download.inline.de.po has changed. wiki/src/install/inc/steps/download.inline.ca.po: updating as wiki/src/install/inc/steps/download.inline.de.po has changed. wiki/src/install/inc/steps/download.inline.id.po: updating as wiki/src/install/inc/steps/download.inline.de.po has changed. wiki/src/install/inc/steps/download.inline.pl.po: updating as wiki/src/install/inc/steps/download.inline.de.po has changed. wiki/src/install/inc/steps/download.inline.ru.po: updating as wiki/src/install/inc/steps/download.inline.de.po has changed. wiki/src/install/inc/steps/download.inline.sr_Latn.po: updating as wiki/src/install/inc/steps/download.inline.de.po has changed. wiki/src/install/inc/steps/download.inline.tr.po: updating as wiki/src/install/inc/steps/download.inline.de.po has changed. wiki/src/install/inc/steps/download.inline.zh.po: updating as wiki/src/install/inc/steps/download.inline.de.po has changed. wiki/src/install/inc/steps/download.inline.zh_TW.po: updating as wiki/src/install/inc/steps/download.inline.de.po has changed.
| * | updated PO filesIkiWiki5 days6-166/+666
|/ /
* | Merge branch 'doc/16175-unclear-openpgp-verification'sajolida5 days8-42/+109
|\ \
| * | Document alternative notification when the signing key is untrusted ↵sajolida12 days7-2/+11
| | | | | | | | | | | | (Will-fix: #15697)
| * | Adapt to new interpolation options in Tails 4.0sajolida12 days1-1/+1
| | |
| * | Duplicate step to download the signaturesajolida12 days1-0/+31
| | | | | | | | | | | | | | | | | | Now that we have a procedure for each operating system and no procedure anymore in the generic header ("Verify using OpenPGP"), I feel the need to duplicate this step at the beginning of each procedure.
| * | Add consistent vertical space between stepssajolida12 days1-13/+13
| | |
| * | Tell what this step is aboutsajolida12 days1-0/+2
| | |
| * | Format as proceduresajolida12 days1-17/+23
| | |