# Dot release?

**URL:** <https://community.zeek.org/t/dot-release/2983>\
**Category:** Development\
**Tags:** development\
**Created:** [January 30, 2014, 4:50pm UTC](https://community.zeek.org/t/dot-release/2983 "2014-01-30T16:50:33Z")\
**Posts on this page:** 8\
**Page:** 1

<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:** [January 30, 2014, 4:50pm UTC](https://community.zeek.org/t/dot-release/2983/1 "2014-01-30T16:50:33Z")

</div>

Folks,

making a 2.2.1 release has been coming up a few times and I'm thinking  
we should just snapshot current master for that. We've been fixing  
quite a number of things since 2.2, yet there aren't any larger new  
features yet (GRE tunnel decapsulation being the only one I can think  
of right now).

I'd wait for two more things though:

&nbsp;&nbsp;&nbsp;&nbsp;- Merging, and some testing, of Jon's recent file analysis  
&nbsp;&nbsp;&nbsp;&nbsp;framework API changes that make the file handle management more  
&nbsp;&nbsp;&nbsp;&nbsp;efficient.

&nbsp;&nbsp;&nbsp;&nbsp;- Figuring out the exec and/or sumstats problems (it looks certain  
&nbsp;&nbsp;&nbsp;&nbsp;at this point that exec isn't cleaning up fully; and sumstats may  
&nbsp;&nbsp;&nbsp;&nbsp;have a larger than expected CPU impact, but that's not clear yet I  
&nbsp;&nbsp;&nbsp;&nbsp;believe).

Once 2.2.1 is out, I'd then next work on merging my dynamic plugin  
code, which is mostly ready but needs cleanup, review, documentation,  
testing.

How does that sound? If good, now would also be the time to finalize  
any other minor fixes that people might want to see in 2.2.1.

Robin

---

<div class="post-metadata">

**Author:** ![Slagell\_Adam\_J](https://avatars.discourse-cdn.com/v4/letter/s/e9c0ed/32.png) [@Slagell\_Adam\_J](https://community.zeek.org/u/Slagell_Adam_J)\
**Post date:** [January 30, 2014, 4:57pm UTC](https://community.zeek.org/t/dot-release/2983/2 "2014-01-30T16:57:22Z")

</div>

I like that plan. I think there are some minor Maverick's issues too that Daniel found. So we might want to get those in there as well.

---

<div class="post-metadata">

**Author:** ![johanna](https://avatars.discourse-cdn.com/v4/letter/j/50afbb/32.png) [@johanna](https://community.zeek.org/u/johanna)\
**Post date:** [January 30, 2014, 6:17pm UTC](https://community.zeek.org/t/dot-release/2983/3 "2014-01-30T18:17:16Z")

</div>

I already told Robin - but just for the record, I think it is a good idea/plan.

Johanna

---

<div class="post-metadata">

**Author:** ![Liam\_Randall2](https://avatars.discourse-cdn.com/v4/letter/l/a87d85/32.png) [@Liam\_Randall2](https://community.zeek.org/u/Liam_Randall2)\
**Post date:** [January 30, 2014, 6:32pm UTC](https://community.zeek.org/t/dot-release/2983/4 "2014-01-30T18:32:46Z")

</div>

Yes, the current master is WAY more stable on busy production sensors that 2.2. For sites really leaning on the intel framework master is the only way to go.

Thanks,

Liam Randall

---

<div class="post-metadata">

**Author:** ![Matthias\_Vallentin1](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/matthias_vallentin1/32/596_2.png) [@Matthias\_Vallentin1](https://community.zeek.org/u/Matthias_Vallentin1)\
**Post date:** [January 30, 2014, 7:22pm UTC](https://community.zeek.org/t/dot-release/2983/5 "2014-01-30T19:22:01Z")

</div>

> I'd wait for two more things though:

Aashish also raised some potential bugs with Bro's hashing. It appears  
that the Bloom filters fill up too quickly, i.e., do not meet their  
false positive requirements. My hunch is that this has to do with the  
construction of hash functions, perhaps they are not pairwise  
independent unless parametrized in a certain way, or perhaps there's  
just some other smaller bug in place. In any case, it needs to be  
fixed and I wonder whether 2.2.1 is the right target for that.

&nbsp;&nbsp;&nbsp;&nbsp;Matthias

---

<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:** [January 30, 2014, 7:34pm UTC](https://community.zeek.org/t/dot-release/2983/6 "2014-01-30T19:34:41Z")

</div>

Yes, that would be good to get in there too if we can figure out  
what's going on.

Robin

---

<div class="post-metadata">

**Author:** ![Seth\_Hall3](https://avatars.discourse-cdn.com/v4/letter/s/d6d6ee/32.png) [@Seth\_Hall3](https://community.zeek.org/u/Seth_Hall3)\
**Post date:** [January 31, 2014, 1:46am UTC](https://community.zeek.org/t/dot-release/2983/7 "2014-01-31T01:46:50Z")

</div>

I'm in the same boat as Johanna here. Looking forward to the 2.2.1 release. 😉

&nbsp;&nbsp;.Seth

---

<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:41pm UTC](https://community.zeek.org/t/dot-release/2983/8 "2022-05-06T15:41:32Z")

</div>


