From 68016033ecc6bf55294adcc71ff3c9c0e39b3f69 Mon Sep 17 00:00:00 2001 From: Shubham Pampattiwar Date: Tue, 2 Jan 2024 12:13:10 -0800 Subject: [PATCH] Update GOVERNANCE.md Signed-off-by: Shubham Pampattiwar --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 56d22a3d2..5e0d31701 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -128,7 +128,7 @@ If depreciation proposal passes by supermajority votes, the feature is deprecate The deprecation window is the period from the release in which the deprecation takes effect through the release in which the feature is removed. During this period, only critical security vulnerabilities and catastrophic bugs should be fixed. -**Note:** If a deprecated feature must remain available for general use for two releases after deprecation, perhaps a backup that uses this deprecated feature must be fully-supported for restore for four releases. +**Note:** If a backup relies on a deprecated feature, then backups made with the last Velero release before this feature is removed must still be restorable in version `n+2`. For instance, something like restic feature support, that might mean that restic is removed from the list of supported uploader types in version `n` but the underlying implementation required to restore from a restic backup won't be removed until release `n+2`. ## Updating Governance