Skip to content

Platform Support Policy

Christian Kreibich edited this page Jan 25, 2022 · 22 revisions

The Zeek project officially supports a range of platforms and current releases. As a rule of thumb, we aim to support at least the two most recent stable releases actively supported on a given platform, and we strive to support freely available long-term support (LTS) versions. Specifically:

Platform Policy Schedule References
CentOS / CentOS Stream Current release and prior one still receiving maintenance updates1 wiki.centos.org, www.centos.org
Debian Current release and prior LTS one wiki.debian.org, wiki.debian.org
Fedora Current release and 1-2 prior supported ones 2 wikipedia.org
FreeBSD Current and previous release at latest releng version cirrus-ci.org, wikipedia.org, freebsd.org
MacOS Current and previous release as supported by Cirrus CI 3 cirrus-ci.org, wikipedia.org
OpenSUSE Leap Current release and prior one on regular support wikipedia.org
Ubuntu Current release and prior ones on Standard Support wiki.ubuntu.com

1: CentOS 8 EOL'd earlier than expected, at the end of 2021, due to the shift to CentOS Stream. We've adopted that shift.
2: Fedora releases every 6 months and maintains for 13, so it has 2-3 currently maintained releases; 3 during the 1-month overlap window, 2 otherwise.
3: According Cirrus CI, images older than Catalina aren't available, but they have started persisting images going forward.

For details on individual operating system versions, please consult our OS support matrix.

To build Zeek on one of the above platforms, please consult our CI setups for platform-specific requirements. For Linux distros our Dockerfiles show required packages and configuration steps, and for VM images (FreeBSD & macOS) the prepare.sh scripts contain the same.

Platform support goes both ways: if you're using a supported platform, Zeek will build and function as expected. Conversely, we refrain from using features (such as recent C++ or Python language features) that are not provided on all of the currently supported platforms. Put simply: if it works with all platforms in our CI, we may end up using it, and won't use it otherwise.

To track current versions, we maintain a release calendar in Google Calendar and iCal formats.

External resources that might help automate this in the future:

Clone this wiki locally