# Zeek 4.0.0 released

**URL:** <https://community.zeek.org/t/zeek-4-0-0-released/6308>\
**Category:** Zeek\
**Tags:** announcement\
**Created:** [March 1, 2021, 10:02pm UTC](https://community.zeek.org/t/zeek-4-0-0-released/6308 "2021-03-01T22:02:00Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jon\_Siwek](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@Jon\_Siwek](https://community.zeek.org/u/Jon_Siwek)\
**Post date:** [March 1, 2021, 10:02pm UTC](https://community.zeek.org/t/zeek-4-0-0-released/6308/1 "2021-03-01T22:02:00Z")

</div>

Zeek 4.0.0 is now available:

&nbsp;&nbsp;[https://zeek.org/get-zeek/](https://zeek.org/get-zeek/)

This is a Long-Term Support (LTS) release, receiving critical  
bug-fixes and security patches for the next year. The previous LTS  
branch of Zeek 3.0.x may still receive any important security patches  
for the next two months, but won't be maintained afterward.

General info about this release can be found in the release notes as  
well as a previous blog post from the release-candidate phase:

&nbsp;&nbsp;[https://github.com/zeek/zeek/releases/tag/v4.0.0](https://github.com/zeek/zeek/releases/tag/v4.0.0)  
&nbsp;&nbsp;[https://zeek.org/2020/12/15/zeek-4-0-release-candidate/](https://zeek.org/2020/12/15/zeek-4-0-release-candidate/)

---

<div class="post-metadata">

**Author:** ![James\_inthe\_box](https://avatars.discourse-cdn.com/v4/letter/j/6f9a4e/32.png) [@James\_inthe\_box](https://community.zeek.org/u/James_inthe_box)\
**Post date:** [March 4, 2021, 6:54pm UTC](https://community.zeek.org/t/zeek-4-0-0-released/6308/2 "2021-03-04T18:54:40Z")

</div>

Is there some reason for only two months until EOL? That’s pretty short for some folks.

James

---

<div class="post-metadata">

**Author:** ![robin](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/robin/32/599_2.png) [@robin](https://community.zeek.org/u/robin)\
**Post date:** [March 4, 2021, 7:02pm UTC](https://community.zeek.org/t/zeek-4-0-0-released/6308/3 "2021-03-04T19:02:21Z")

</div>

I’d say it’s actually the opposite: we’re extending what’s normaly one year of support for an LTS release by another 2 months to give people some overlap. See here for our release policy: [https://github.com/zeek/zeek/wiki/Release-Cadence](https://github.com/zeek/zeek/wiki/Release-Cadence)

Robin

---

<div class="post-metadata">

**Author:** ![James\_inthe\_box](https://avatars.discourse-cdn.com/v4/letter/j/6f9a4e/32.png) [@James\_inthe\_box](https://community.zeek.org/u/James_inthe_box)\
**Post date:** [March 5, 2021, 2:21pm UTC](https://community.zeek.org/t/zeek-4-0-0-released/6308/4 "2021-03-05T14:21:13Z")

</div>

Ah…so…I think I’m misunderstanding something then. I’m currently on 3.2.3…which was released around December I think. As I read the email I read this as “you have two months to get off of Zeek 3”. Is this not the case?

James

---

<div class="post-metadata">

**Author:** ![Jon\_Siwek](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@Jon\_Siwek](https://community.zeek.org/u/Jon_Siwek)\
**Post date:** [March 5, 2021, 8:05pm UTC](https://community.zeek.org/t/zeek-4-0-0-released/6308/5 "2021-03-05T20:05:11Z")

</div>

The situation/plan is:

\* The core dev team will make 3.0.x (LTS) releases to patch any  
security issues through April.  
\* The core dev team won't make any further 3.1.y or 3.2.z releases.

The release policy doesn't say anything about:

\* Users need to get off particular releases: but there's risk  
associated with staying unpatched or the effort of backporting  
important patches themselves if they stay.  
\* The policy won't change: if there's an argument that convinces the  
core dev team to provide patches for longer, then that's what happens.  
\* Other possible arrangements: where the core dev team aren't the ones  
helping support older versions. E.g. some scheme of giving wider  
volunteer support access to manage the older `release/` branches in  
the Zeek organization's Git repo or other community-driven  
forking/patching model.

My understanding of the current plan: historically, there hasn't been  
as much effort to avoid breaking changes as there has been for the  
3.0.x to 4.0.0 (LTS) path, so the upgrade itself is hopefully a simple  
process where a two month period is enough. All plans for breaking  
changes are revealed in deprecation warnings and release notes of  
4.0.0, so people have more like 14+ months until 5.0.0 to adapt to any  
of those more complex changes. The non-LTS branches (e.g. 3.1.x and  
3.2.y) were meant for those that can do upgrades quickly and care more  
about using the latest features than about long support duration.

- Jon

---

<div class="post-metadata">

**Author:** ![James\_inthe\_box](https://avatars.discourse-cdn.com/v4/letter/j/6f9a4e/32.png) [@James\_inthe\_box](https://community.zeek.org/u/James_inthe_box)\
**Post date:** [March 5, 2021, 9:20pm UTC](https://community.zeek.org/t/zeek-4-0-0-released/6308/6 "2021-03-05T21:20:52Z")

</div>

Awesome thanks for the clarification…will be installing 4 soon enough 😌

James

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\
**Post date:** [May 6, 2022, 3:47pm UTC](https://community.zeek.org/t/zeek-4-0-0-released/6308/7 "2022-05-06T15:47:36Z")

</div>


