Commit bf5c5436 authored by Tails developers's avatar Tails developers

Consistently use "upgrade" instead of "update".

parent ece1af2d
[[!toc levels=4]]
See also the [[incremental updates design document|contribute/design/incremental_updates]].
See also the [[incremental upgrades design document|contribute/design/incremental_upgrades]].
# Roadmap
1. (**past**) Tails 0.13 has the harmless part of the
`feature/incremental-upgrades` branch merged (users creation with
sudo credentials, dependencies installation), leaving aside the
part about running the update frontend automatically at startup.
=> Tails 0.13 should have been able to incrementally update to
something newer, when running the update frontend by hand,
part about running the upgrade frontend automatically at startup.
=> Tails 0.13 should have been able to incrementally upgrade to
something newer, when running the upgrade frontend by hand,
but the included Tails OpenPGP signing key expired too quickly for
this to happen.
2. (**past**) Now that 0.14 is out:
* Prepare IUK: **done**
* Update update-description files: **done**
* Ask beta testers to try the incremental update process: **done**
* Update upgrade-description files: **done**
* Ask beta testers to try the incremental upgrade process: **done**
* Find most critical bugs: **done**.
3. Complete **phase one: make ready for more alpha testing**
......@@ -26,8 +26,8 @@ See also the [[incremental updates design document|contribute/design/incremental
one"]] were resolved:
* Prepare IUK
* Update update-description files
* Ask alpha testers to try the incremental update process
* Update upgrade-description files
* Ask alpha testers to try the incremental upgrade process
* Catch and fix most remaining bugs
4. Complete **phase two: make ready for beta testing**
......@@ -36,8 +36,8 @@ See also the [[incremental updates design document|contribute/design/incremental
two"]], and then:
* Prepare IUK
* Update update-description files
* Ask beta testers to try the incremental update process
* Update upgrade-description files
* Ask beta testers to try the incremental upgrade process
* Catch and fix most remaining bugs
* Review user documentation and translations
......@@ -50,7 +50,7 @@ See also the [[incremental updates design document|contribute/design/incremental
6. Later
See tickets with *Incremental updates* category on [[!tails_redmine]].
See tickets with *Incremental upgrades* category on [[!tails_redmine]].
# Code
......@@ -66,26 +66,26 @@ changes are useful enough to put time in it.
### Packaging could be more self-contained
Move `/etc/sudoers.d/zzz_update` and IUK-related user creation from
Move `/etc/sudoers.d/zzz_upgrade` and IUK-related user creation from
the Tails main Git repository to the `tails-iuk` Debian package, so
that it's more self-contained and easier to test.
### Button for aborting update cleanly
### Button for aborting upgrade cleanly
### Compute and display ETA
### Multi-step incremental update
### Multi-step incremental upgrade
E.g. 0.11 boots after 0.11.1 and 0.11.2 are out. Tails fetches
https://tails.boum.org/update/v1/Tails/0.11/i386/stable/updates.yml,
that shall contain an incremental update path with two target files:
the 0.11 to 0.11.1 IUK, and the 0.11.1 to 0.11.2 IUK. The updater
https://tails.boum.org/upgrade/v1/Tails/0.11/i386/stable/upgrades.yml,
that shall contain an incremental upgrade path with two target files:
the 0.11 to 0.11.1 IUK, and the 0.11.1 to 0.11.2 IUK. The upgrader
would download these two files and install the two IUKs in the
correct order.
### sharing update material
### sharing upgrade material
Once the incremental update has been applied, I may be proposed to
Once the incremental upgrade has been applied, I may be proposed to
save a copy of the target files to a location of my choosing.
### allow one to download target files in the clear
......
......@@ -1071,13 +1071,13 @@ prefer strong ciphers and MACs..
- [[!tails_gitweb config/chroot_local-includes/etc/ssh/ssh_config]]
- [[!tails_gitweb config/chroot_local-includes/usr/local/bin/connect-socks]]
### 3.6.21 Incremental updates
### 3.6.21 Incremental upgrades
PENDING-FOR-0.22-or-0.23:
When a Tails release is out, Tails users are proposed to download and
apply a partial update (that is, only what has changed between two
releases). See [[contribute/design/incremental_updates]] for details.
apply a partial upgrade (that is, only what has changed between two
releases). See [[contribute/design/incremental_upgrades]] for details.
## 3.7 Running Tails in virtual machines
......@@ -1139,7 +1139,7 @@ release candidates images before they are officially published.
Keeping Tor (stable releases only, unless the Tor core developers
recommend otherwise) and Iceweasel up-to-date is a priority.
Remaining applications, including the base system, will be updated
Remaining applications, including the base system, will be upgraded
using Debian standard upgrade process, and generally based on the
latest Debian stable release so there are not many problems.
......
......@@ -188,7 +188,7 @@ features properly do their work; second, our `torrc` sets the right
* Make sure these use the `SocksPort` dedicated for Tails-specific applications:
- htpdate
- tails-security-check
- incremental updates
- incremental upgrades
* Make sure iceweasel uses its dedicated `SocksPort`.
* Make sure other applications (Polipo, Gobby 0.4 and 0.5, SSH, whois)
use the default system-wide `SocksPort`.
......@@ -356,36 +356,36 @@ Tests to run:
Tails on it: should warn this action is not supported, and direct
the user to the "Clone & Install" operation mode.
<a id="incremental-updates"></a>
<a id="incremental-upgrades"></a>
# Incremental updates
# Incremental upgrades
The following should be tested once incremental updates are ready for
The following should be tested once incremental upgrades are ready for
real-world deployment.
Try every update path supported by the generated update-description
Try every upgrade path supported by the generated upgrade-description
files:
* the resulting incrementally updated system must boot and *About
Tails* must pretend it has indeed been updated
* for updates that only propose a non-incremental paths: make sure the
* the resulting incrementally upgraded system must boot and *About
Tails* must pretend it has indeed been upgraded
* for upgrades that only propose a non-incremental paths: make sure the
user is guided just fine to the download web page
Given these are not published yet, a local test setup is needed:
* a web server
* a replacement for the Tails website's `/update/` tree with
update-description files in there, e.g.
`/var/www/tails/update/v1/Tails/0.14~rc2/i386/stable/updates.yml`
* a replacement for the Tails website's `/upgrade/` tree with
upgrade-description files in there, e.g.
`/var/www/tails/upgrade/v1/Tails/0.14~rc2/i386/stable/upgrades.yml`
* a replacement for the Tails HTTP mirrors' `iuk` directories,
e.g. `/var/www/tails/stable/iuk/Tails_i386_0.14-rc2_to_0.14.iuk`
Also, the updater must be called, from inside the system to update,
Also, the upgrader must be called, from inside the system to upgrade,
with every needed option to use the local web server rather than the
online one, e.g.:
DISABLE_PROXY=1 SSL_NO_VERIFY=1 \
tails-update-frontend-wrapper --override-baseurl http://10.36.24.33/tails
tails-upgrade-frontend-wrapper --override-baseurl http://10.36.24.33/tails
# Persistence
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment