From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 2/2] faq: eol: fix Bookworm EOL date
Date: Thu, 21 May 2026 10:58:00 +0200 [thread overview]
Message-ID: <20260521090007.320100-2-f.gruenbichler@proxmox.com> (raw)
In-Reply-To: <20260521090007.320100-1-f.gruenbichler@proxmox.com>
it got moved back and then forth again after the initial release, the last
point release and handover to LTS is currently planned for July 2026.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
Notes:
see https://lists.debian.org/debian-project/2026/05/msg00032.html
I left the PVE EOL as it was before
pve-faq.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pve-faq.adoc b/pve-faq.adoc
index 32ef1d2..1d113da 100644
--- a/pve-faq.adoc
+++ b/pve-faq.adoc
@@ -91,7 +91,7 @@ recommended.
|===============================================================================
| {pve} Version | Debian Version | First Release | Debian EOL | Proxmox EOL
| {pve} 9 | Debian 13 (Trixie) | 2025-08 | tba | tba
-| {pve} 8 | Debian 12 (Bookworm)| 2023-06 | 2026-08 | 2026-08
+| {pve} 8 | Debian 12 (Bookworm)| 2023-06 | 2026-07 | 2026-08
| {pve} 7 | Debian 11 (Bullseye)| 2021-07 | 2024-07 | 2024-07
| {pve} 6 | Debian 10 (Buster) | 2019-07 | 2022-09 | 2022-09
| {pve} 5 | Debian 9 (Stretch) | 2017-07 | 2020-07 | 2020-07
--
2.47.3
next prev parent 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 [PATCH docs 1/2] faq: make EOL description more explicit Fabian Grünbichler
2026-05-21 8:58 ` Fabian Grünbichler [this message]
2026-05-21 9:03 ` applied: " 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-2-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