From 52aa1cd17fabb5ec7c57d83e2ec8e83f2bcdca17 Mon Sep 17 00:00:00 2001 From: Michael Eischer Date: Sat, 6 Sep 2025 20:55:46 +0200 Subject: [PATCH] docs: sync compatibility section with website This is no change in policy, just a more precise description of the status quo. --- doc/090_participating.rst | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/doc/090_participating.rst b/doc/090_participating.rst index a035af7ca..2a3964cac 100644 --- a/doc/090_participating.rst +++ b/doc/090_participating.rst @@ -130,14 +130,17 @@ Backward compatibility for backups is important so that our users are always able to restore saved data. Therefore restic follows `Semantic Versioning `__ to clearly define which versions are compatible. The repository and data structures contained therein are -considered the "Public API" in the sense of Semantic Versioning. This -goes for all released versions of restic, this may not be the case for -the master branch. +considered the "Public API" in the sense of Semantic Versioning. -We guarantee backward compatibility of all repositories within one major -version; as long as we do not increment the major version, data can be -read and restored. We strive to be fully backward compatible to all -prior versions. +Once version 1.0.0 is released, we guarantee backward compatibility of +all repositories within one major version; as long as we do not +increment the major version, data can be read and restored. We strive +to be fully backward compatible to all prior versions. + +During initial development (versions prior to 1.0.0), maintainers and +developers will do their utmost to keep backwards compatibility and +stability, although there might be breaking changes without increasing +the major version. ********************** Building documentation