public inbox for pmg-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christoph Heiss <c.heiss@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH pmg-docs 1/2] faq: split up upgrade section into major and point release upgrades
Date: Tue, 22 Oct 2024 13:24:24 +0200	[thread overview]
Message-ID: <20241022112426.709562-2-c.heiss@proxmox.com> (raw)
In-Reply-To: <20241022112426.709562-1-c.heiss@proxmox.com>

Makes the difference stand out better, much like we do it in the PVE
docs too.

Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
 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


  reply	other threads:[~2024-10-22 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 11:24 [pmg-devel] [PATCH pmg-docs 0/2] improve faq upgrade section Christoph Heiss
2024-10-22 11:24 ` Christoph Heiss [this message]
2024-10-22 11:24 ` [pmg-devel] [PATCH pmg-docs 2/2] fix #5771: faq: add 7 to 8 upgrade link Christoph Heiss

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=20241022112426.709562-2-c.heiss@proxmox.com \
    --to=c.heiss@proxmox.com \
    --cc=pmg-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal