From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 1/2] faq: make EOL description more explicit
Date: Thu, 21 May 2026 10:57:59 +0200 [thread overview]
Message-ID: <20260521090007.320100-1-f.gruenbichler@proxmox.com> (raw)
instead of just "supported", which has been misinterpreted in the past, make
the regular security team to LTS part more explicit.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
pve-faq.adoc | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/pve-faq.adoc b/pve-faq.adoc
index 606a1c1..32ef1d2 100644
--- a/pve-faq.adoc
+++ b/pve-faq.adoc
@@ -80,10 +80,10 @@ to run.
[[faq-support-table]]
How long will my {pve} version be supported?::
-{pve} versions are supported at least as long as the corresponding
-Debian version, i.e. approximately 3 years after its initial release,
-see https://www.debian.org/security/faq#lifespan[Debian lifespan].
-{pve} uses a
+{pve} versions are supported *at least as long* as the corresponding Debian
+version is supported by the Debian Security Team, i.e. approximately 3 years
+after its initial release, see
+https://www.debian.org/security/faq#lifespan[Debian lifespan]. {pve} uses a
rolling release model and using the latest stable version is always
recommended.
+
--
2.47.3
next reply other threads:[~2026-05-21 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 8:57 Fabian Grünbichler [this message]
2026-05-21 8:58 ` [PATCH docs 2/2] faq: eol: fix Bookworm EOL date Fabian Grünbichler
2026-05-21 9:03 ` applied: [PATCH docs 1/2] faq: make EOL description more explicit Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260521090007.320100-1-f.gruenbichler@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox