From 40fda7a87459dc0c6d9b58e53b59ec281aa6cac0 Mon Sep 17 00:00:00 2001 From: Leonardo Di Giovanna Date: Thu, 8 Jan 2026 12:14:24 +0100 Subject: [PATCH] docs(proposals): specify version enforcing the deprecation Signed-off-by: Leonardo Di Giovanna --- ...51215-legacy-bpf-grpc-output-gvisor-engine-deprecation.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/proposals/20251215-legacy-bpf-grpc-output-gvisor-engine-deprecation.md b/proposals/20251215-legacy-bpf-grpc-output-gvisor-engine-deprecation.md index 29f304ce..b7ecba0f 100644 --- a/proposals/20251215-legacy-bpf-grpc-output-gvisor-engine-deprecation.md +++ b/proposals/20251215-legacy-bpf-grpc-output-gvisor-engine-deprecation.md @@ -102,8 +102,9 @@ The deprecation of these components introduces user-facing changes that must be deprecation policy for "non-backward compatible user-facing changes" (see [20231220-features-adoption-and-deprecation.md#deprecation-policy](./20231220-features-adoption-and-deprecation.md#deprecation-policy)). -All components are stable, and given that the current stable Falco version is `0.43.0` (ante `1.0.0`), the minimum -deprecation period length is 1 release: this means that components cannot be removed before Falco `0.44.0`. +All components are stable, and considering that deprecations will first be enforced in the stable Falco version `0.43.0` +(ante `1.0.0`), the minimum deprecation period length is 1 release: this means that components cannot be removed before +Falco `0.44.0`. At high level, the action plan is to inform users, during the deprecation period, about the deprecation: this is achieved by emitting a deprecation notice if the user try to leverage any of the feature exposed by any component, and