From 25d23168f4962a1404cf6eacf0ad6b4986b108a3 Mon Sep 17 00:00:00 2001 From: Leonardo Grasso Date: Mon, 29 May 2023 10:54:29 +0200 Subject: [PATCH] docs(proposals): roadamap mgt non-goals Co-authored-by: Melissa Kilby Co-authored-by: Massimiliano Giovagnoli Signed-off-by: Leonardo Grasso --- proposals/20230511-roadmap-management.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/proposals/20230511-roadmap-management.md b/proposals/20230511-roadmap-management.md index 3c078bb4..5affa10f 100644 --- a/proposals/20230511-roadmap-management.md +++ b/proposals/20230511-roadmap-management.md @@ -14,6 +14,13 @@ The pillars of this proposal are: - Using *GitHub Project* as the primary tool for managing *The Falco Project* roadmap +### Non-Goals + +- Providing an exact set of criteria for task prioritization +- Detailing testing procedures +- Providing detailed instructions for GitHub Project usage +- Addressing hotfix releases + ### Scope of this Proposal Primarily, the roadmap targets the planning of Falco development and releases. However, given Falco's dependence on numerous components, it's inevitable that scheduling and planning activities span across multiple repositories. We anticipate that all [core repositories](https://github.com/falcosecurity/evolution#official) will be interconnected with the roadmap, making it comprehensive enough to incorporate items from all related [Falcosecurity repositories](https://github.com/falcosecurity) as necessary.