<div dir="ltr">Sounds great, thanks Jon!</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 9, 2020 at 2:56 PM Jon Siwek <<a href="mailto:jsiwek@corelight.com">jsiwek@corelight.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Just a FYI / heads-up: I'm planning to make 3.0.3 and 3.1.1 releases<br>
tomorrow that will include the patch for this issue.<br>
<br>
- Jon<br>
<br>
On Thu, Mar 5, 2020 at 10:57 AM Doug Burks <<a href="mailto:doug.burks@gmail.com" target="_blank">doug.burks@gmail.com</a>> wrote:<br>
><br>
> OK, thanks Jon.<br>
><br>
> On Thu, Mar 5, 2020 at 1:23 PM Jon Siwek <<a href="mailto:jsiwek@corelight.com" target="_blank">jsiwek@corelight.com</a>> wrote:<br>
>><br>
>> On Thu, Mar 5, 2020 at 6:44 AM Doug Burks <<a href="mailto:doug.burks@gmail.com" target="_blank">doug.burks@gmail.com</a>> wrote:<br>
>><br>
>> > Would you recommend that we apply the patch to our Zeek 3.0.2 package OR hold off on 3.0.2 and wait for 3.0.3 assuming it will be included there?<br>
>><br>
>> Hi Doug, I do now have this on the schedule for fixing in a Zeek 3.0.3<br>
>> (and 3.1.1), but not sure what time frame to expect those releases.<br>
>> I'll suggest to the team to aim at doing one in ~2-3 weeks. If you'd<br>
>> like to patch ASAP, you may still want to wait at least until that<br>
>> Pull Request gets a code review and merged into the master branch.<br>
>><br>
>> - Jon<br>
><br>
><br>
><br>
> --<br>
> Doug Burks<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Doug Burks</div>