The regular, full-service support lifecycle for Debian 12, codenamed "Bookworm," concluded on 12 July 2026. In a significant strategic shift, security maintenance has been transferred from the project's core Security and Release Teams to the volunteer-driven Long Term Support (LTS) Team. This transition occurs three years after the distribution's initial launch.
The change is more than administrative; it represents a fundamental alteration in the maintenance contract for Debian's "stable" release. System administrators and infrastructure managers must now operate under a significantly reduced support scope. LTS resources are exclusively allocated to critical security patches and high-severity bug fixes, with routine maintenance, feature updates, and non-critical bug fixes no longer provided.
This reallocation allows the Debian Project to focus its primary development efforts on the current stable release. However, it transfers full lifecycle responsibility to the user. The reliability and continuity of security updates now depend on the capacity and contributions of the LTS volunteer community, making it a conditional safety net rather than a guaranteed service.
For organizations, this event is an operational trigger point. The immediate priority is to verify that all Bookworm systems are configured to pull updates from the dedicated LTS repositories. Beyond this immediate step, the onset of LTS must be treated as the start of a finite migration runway. Administrators should leverage this period to develop and execute a plan to transition critical infrastructure to a current, fully supported Debian stable release or another supported platform.
The conclusion of Bookworm's primary support phase underscores a core tenet of system administration: proactive lifecycle management. As upstream support models evolve, the responsibility for maintaining a secure and stable environment shifts decisively to local operations teams.
Debian 12（代號「Bookworm」）的常規、全面服務支援週期已於2026年7月12日結束。在一項重要的策略轉變中，安全維護工作已從專案的核心安全與發佈團隊，轉移至由志願者驅動的長期支援（LTS）團隊。此次過渡發生在該發行版首次推出三年後。
這項變動不僅是行政調整，它代表了 Debian「穩定版本」維護合約的根本性改變。系統管理員及基礎設施管理者現在必須在支援範圍顯著縮減的情況下運作。LTS 資源將專注於關鍵的安全性修補程式與高嚴重性錯誤修復，而日常維護、功能更新及非關鍵性錯誤修復將不再提供。
此資源重新分配讓 Debian 專案能將主要開發精力集中於當前的穩定版本。然而，這也將完整的生命週期責任轉移給了使用者。安全性更新的可靠性與連續性，現取決於 LTS 志願者社群的貢獻能力與投入程度，使其成為一種有條件的安全網，而非有保障的服務。
對各機構而言，此事件是一個操作觸發點。當務之急是驗證所有 Bookworm 系統均已配置為從專用的 LTS 儲存庫拉取更新。在此直接步驟之後，必須將 LTS 階段的開始視為有限度遷移時間線的起點。管理員應善用此期間，制定並執行計畫，將關鍵基礎設施遷移至當前受完全支援的 Debian 穩定版本或其他受支援的平台。
Bookworm 主要支援階段的結束，強調了系統管理的一項核心原則：主動的生命週期管理。隨著上游支援模式的演變，維護一個安全且穩定環境的責任，已明確地轉移至本地運維團隊。