summaryrefslogtreecommitdiffstats
path: root/doc/wiki/Upgrading.txt
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-15 17:36:47 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-15 17:36:47 +0000
commit0441d265f2bb9da249c7abf333f0f771fadb4ab5 (patch)
tree3f3789daa2f6db22da6e55e92bee0062a7d613fe /doc/wiki/Upgrading.txt
parentInitial commit. (diff)
downloaddovecot-0441d265f2bb9da249c7abf333f0f771fadb4ab5.tar.xz
dovecot-0441d265f2bb9da249c7abf333f0f771fadb4ab5.zip
Adding upstream version 1:2.3.21+dfsg1.upstream/1%2.3.21+dfsg1
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'doc/wiki/Upgrading.txt')
-rw-r--r--doc/wiki/Upgrading.txt26
1 files changed, 26 insertions, 0 deletions
diff --git a/doc/wiki/Upgrading.txt b/doc/wiki/Upgrading.txt
new file mode 100644
index 0000000..ae95ccb
--- /dev/null
+++ b/doc/wiki/Upgrading.txt
@@ -0,0 +1,26 @@
+Upgrading between micro versions
+================================
+
+(For example v1.0.x -> v1.0.y or v1.1.x -> v1.1.y)
+
+The NEWS file [http://dovecot.org/doc/NEWS] contains all the important changes
+marked with "*" character. Read them to see if there is anything that concerns
+you. In general all the changes try to preserve backwards compatibility, but
+some changes which are meant to improve the stability and correctness of the
+configuration could mean breaking some existing installations. And that may be
+a good thing, since it can expose problems which could otherwise show up as
+random errors.
+
+Upgrading between other versions
+================================
+
+ * <v0.99.x to v1.0> [Upgrading.1.0.txt]
+ * <v1.0 to v1.1> [Upgrading.1.1.txt]
+ * <v1.1 to v1.2> [Upgrading.1.2.txt]
+ * <v1.2 to v2.0> [Upgrading.2.0.txt]
+ * <v2.0 to v2.1> [Upgrading.2.1.txt]
+ * <v2.1 to v2.2> [Upgrading.2.2.txt]
+ * <v2.2 to v2.3> [Upgrading.2.3.txt]
+ * <v2.3 to v2.4> [Upgrading.2.4.txt]
+
+(This file was created from the wiki on 2019-06-19 12:42)