mirror of
https://github.com/restic/restic.git
synced 2025-10-19 15:43:21 +00:00
docs: sync compatibility section with website
This is no change in policy, just a more precise description of the status quo.
This commit is contained in:
parent
2ad703bfd8
commit
52aa1cd17f
1 changed files with 10 additions and 7 deletions
|
@ -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 <https://semver.org>`__ 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
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue