diff options
| author | Armaël Guéneau <armael.gueneau@ens-lyon.org> | 2024-01-27 14:51:15 +0100 |
|---|---|---|
| committer | Armaël Guéneau <armael.gueneau@ens-lyon.org> | 2024-01-27 14:51:15 +0100 |
| commit | 91a51dd3e876bde7d9b6199b478c26c620994348 (patch) | |
| tree | 6db80499bd2d9531aeedc6a294d16f151f495ee0 /doc/book/operations/upgrading.md | |
| parent | 08a871390e44751eb03f75189aa40ea2f84a9ffb (diff) | |
| download | garage-91a51dd3e876bde7d9b6199b478c26c620994348.tar.gz garage-91a51dd3e876bde7d9b6199b478c26c620994348.zip | |
doc: fix some typos
Diffstat (limited to 'doc/book/operations/upgrading.md')
| -rw-r--r-- | doc/book/operations/upgrading.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/book/operations/upgrading.md b/doc/book/operations/upgrading.md index 9a738282..6b6ea26d 100644 --- a/doc/book/operations/upgrading.md +++ b/doc/book/operations/upgrading.md @@ -9,7 +9,7 @@ On a new version release, there is 2 possibilities: - protocols and data structures remained the same ➡️ this is a **minor upgrade** - protocols or data structures changed ➡️ this is a **major upgrade** -You can quickly now what type of update you will have to operate by looking at the version identifier: +You can quickly know what type of update you will have to operate by looking at the version identifier: when we require our users to do a major upgrade, we will always bump the first nonzero component of the version identifier (e.g. from v0.7.2 to v0.8.0). Conversely, for versions that only require a minor upgrade, the first nonzero component will always stay the same (e.g. from v0.8.0 to v0.8.1). |