From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id A06B61FF161 for ; Tue, 22 Oct 2024 13:24:31 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DAF1DB9D9; Tue, 22 Oct 2024 13:25:10 +0200 (CEST) From: Christoph Heiss To: pmg-devel@lists.proxmox.com Date: Tue, 22 Oct 2024 13:24:24 +0200 Message-ID: <20241022112426.709562-2-c.heiss@proxmox.com> X-Mailer: git-send-email 2.46.0 In-Reply-To: <20241022112426.709562-1-c.heiss@proxmox.com> References: <20241022112426.709562-1-c.heiss@proxmox.com> MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.031 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pmg-devel] [PATCH pmg-docs 1/2] faq: split up upgrade section into major and point release upgrades X-BeenThere: pmg-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Mail Gateway development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pmg-devel-bounces@lists.proxmox.com Sender: "pmg-devel" Makes the difference stand out better, much like we do it in the PVE docs too. Signed-off-by: Christoph Heiss --- pmg-faq.adoc | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/pmg-faq.adoc b/pmg-faq.adoc index 7db2ab4..8afdd09 100644 --- a/pmg-faq.adoc +++ b/pmg-faq.adoc @@ -51,11 +51,15 @@ NOTE: {pmg} releases before 5.0 are not listed here. As they are all EOL (End Of Life), it's highly recommended to upgrade to a newer version, if still in use. [[faq-upgrade]] -How can I upgrade {pmg} to the next release?:: +How can I upgrade {pmg} to the next point release?:: Minor version upgrades, for example, upgrading from {pmg} version 5.1 -to 5.2, can be done just like any normal update, either through the -__Node -> Updates__ panel or through the command line with: +to 5.2, can be done just like any normal update. But you should still check the +https://pmg.proxmox.com/wiki/index.php/Roadmap[release notes] for any relevant +notable, or breaking change. ++ +For the update itself use either through the __Node -> Updates__ panel or +through the command line with: + ---- apt update @@ -65,13 +69,18 @@ apt full-upgrade NOTE: Always ensure that you correctly set up the xref:pmg_package_repositories[package repositories], and only continue with the actual upgrade if `apt update` did not hit any errors. -+ + +[[faq-major-upgrade]] +How can I upgrade {pmg} to the next major release?:: + Major version upgrades, for example, going from {pmg} 5.4 to 6.0, are also supported. They must be carefully planned and tested, and should *never* be started without having an up-to-date backup ready. ++ Although the specific upgrade steps depend on your respective setup, we provide general instructions and advice on how an upgrade should be performed: + * https://pmg.proxmox.com/wiki/index.php/Upgrade_from_6.x_to_7.0[Upgrade from {pmg} 6.x to 7.0] + * https://pmg.proxmox.com/wiki/index.php/Upgrade_from_5.x_to_6.0[Upgrade from {pmg} 5.x to 6.0] -- 2.46.0 _______________________________________________ pmg-devel mailing list pmg-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel