From 15d5dcdd3bb387aab28bbe7262011c38c7d6d22c Mon Sep 17 00:00:00 2001 From: Christophe Courtois Date: Sun, 26 Feb 2023 08:41:32 +0100 Subject: [PATCH] Add explicit instructions for upgrading between 2.x versions. Add an explicit statement that there is nothing special to do when upgrading between 2.x versions. Leave the previous paragraph about the default location that changed between 2.00 and 2.02, as it is more a matter of transitioning from 1.x to 2.x. --- doc/xml/release.xml | 12 ++++++++++++ doc/xml/user-guide.xml | 7 +++++++ 2 files changed, 19 insertions(+) diff --git a/doc/xml/release.xml b/doc/xml/release.xml index 4a4139230..edc1b988a 100644 --- a/doc/xml/release.xml +++ b/doc/xml/release.xml @@ -35,6 +35,18 @@ + + + + + + + + + +

Add explicit instructions for upgrading between 2.x versions.

+
+ diff --git a/doc/xml/user-guide.xml b/doc/xml/user-guide.xml index 4c645066b..a511de908 100644 --- a/doc/xml/user-guide.xml +++ b/doc/xml/user-guide.xml @@ -866,6 +866,13 @@

and repository options must be indexed when using the new names introduced in v2, e.g. pg1-host, pg1-path, repo1-path, repo1-type, etc.

+ + +
+ Upgrading {[project]} from v2.x to v2.y + +

Upgrading from v2.x to v2.y is straight-forward. The repository format has not changed, so for most installations it is simply a matter of installing binaries for the new version. It is also possible to downgrade if you have not used new features that are unsupported by the older version.

+