From d25e07381e5e7e3b4dc271ba991fc2cf066600cd Mon Sep 17 00:00:00 2001 From: Leo Di Donato Date: Mon, 7 Sep 2020 10:44:36 +0200 Subject: [PATCH] update(proposals): clarify that prebuilding drivers is on a best-effort basis Signed-off-by: Leonardo Di Donato Co-authored-by: Leonardo Grasso --- proposals/20200818-artifacts-storage.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/20200818-artifacts-storage.md b/proposals/20200818-artifacts-storage.md index 5947476e706..48f3cc8c9e0 100644 --- a/proposals/20200818-artifacts-storage.md +++ b/proposals/20200818-artifacts-storage.md @@ -55,7 +55,7 @@ You can also visualize the full list of prebuilt drivers by driver version visit ### Notice -The generation of new prebuilt drivers takes usually place with a frequency of 1-2 weeks. +The generation of new prebuilt drivers takes usually place with a frequency of 1-2 weeks, on a **best-effort** basis. Thus, it can happen the list of available prebuilt drivers does not yet contain the driver version currently on Falco master. @@ -80,4 +80,4 @@ These images are built and published in two cases: - a pull request gets merged into the master branch (**Falco development releases**) - a new Falco release (git tag) happens (**Falco stable releases**) -For a detailed explanation of the container images we build and ship look at the following [documentation](https://github.com/falcosecurity/falco/blob/master/docker/README.md). \ No newline at end of file +For a detailed explanation of the container images we build and ship look at the following [documentation](https://github.com/falcosecurity/falco/blob/master/docker/README.md).