|author||Ulrike Uhlig <firstname.lastname@example.org>||2018-04-24 11:49:05 +0200|
|committer||Ulrike Uhlig <email@example.com>||2018-04-24 11:49:05 +0200|
We don't support Jessie anymore.
1 files changed, 3 insertions, 3 deletions
diff --git a/wiki/src/contribute/release_process/tails-installer.mdwn b/wiki/src/contribute/release_process/tails-installer.mdwn
index bdc616a..56a3d38 100644
@@ -16,19 +16,19 @@ tails-installer.
The `master` branch must always be the one that targets current Tails
and possibly *also* earlier Debian releases. At the moment it supports
-Debian Jessie, Stretch, Buster and Sid.
+Debian Stretch, Buster and Sid.
But that's not enough, since we also need to put releases out with code
that works on current Debian testing/unstable. Thus, we maintain several upstream
release branches in parallel, each with their own major version number:
- * for work and releases that target Jessie and Stretch (and, as long
+ * for work and releases that target Stretch (and, as long
as compatible, that target Debian testing/unstable as well):
* branch = `master`
* version = `5.*`
* tag = `tails-installer_5.*`
-Once we can't support both Jessie, Stretch and Debian testing/unstable
+Once we can't support both Stretch and Debian testing/unstable
with the same codebase anymore, we'll fork a new upstream release
branch that targets Debian testing, it'll be called
`feature/$codename`, use version `6.*`, etc.