From: Robert Obkircher <r.obkircher@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs] fix #6728: remove mention of oldstable to clarify support/EOL policy
Date: Mon, 3 Nov 2025 12:40:18 +0100 [thread overview]
Message-ID: <20251103114055.34989-1-r.obkircher@proxmox.com> (raw)
Someone found the original phrasing confusing, because a Debian
version stays stable and oldstable for roughly 4 years and Promox VE
is supported for about 3 years.
The bug report [0] also mentions a forum post [1] that should be
updated as well.
[0]: https://bugzilla.proxmox.com/show_bug.cgi?id=6728
[1]: https://forum.proxmox.com/threads/proxmox-ve-support-lifecycle.35755/
Signed-off-by: Robert Obkircher <r.obkircher@proxmox.com>
---
pve-faq.adoc | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/pve-faq.adoc b/pve-faq.adoc
index 1f6c4ae..b8cefd9 100644
--- a/pve-faq.adoc
+++ b/pve-faq.adoc
@@ -81,8 +81,9 @@ to run.
How long will my {pve} version be supported?::
{pve} versions are supported at least as long as the corresponding
-Debian Version is
-https://wiki.debian.org/DebianOldStable[oldstable]. {pve} uses a
+Debian version, 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
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-11-03 11:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251103114055.34989-1-r.obkircher@proxmox.com \
--to=r.obkircher@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.