update(proposals): clarify that prebuilding drivers is on a best-effort basis

Signed-off-by: Leonardo Di Donato <leodidonato@gmail.com>
Co-authored-by: Leonardo Grasso <me@leonardograsso.com>
This commit is contained in:
Leo Di Donato 2020-09-07 10:44:36 +02:00 committed by poiana
parent 481eedb80e
commit d25e07381e

View File

@ -55,7 +55,7 @@ You can also visualize the full list of prebuilt drivers by driver version visit
### Notice ### 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. 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 pull request gets merged into the master branch (**Falco development releases**)
- a new Falco release (git tag) happens (**Falco stable 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). 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).