[Zeek-Dev] Re: Platform support policy

[Christian Kreibich]

On 11/5/20 8:51 PM, Christian Kreibich wrote:

I'm putting together a PR (still a draft) for bringing our CI in line
with what's in that page:


Ahem -- that was supposed to be: https://github.com/zeek/zeek/pull/1268/

Best,
Christian
___
zeek-dev mailing list -- zeek-dev@lists.zeek.org
To unsubscribe send an email to zeek-dev-le...@lists.zeek.org

[Zeek-Dev] Re: Platform support policy

[Christian Kreibich]

Hi folks,

Sorry for the delay here -- I've now put together a page:

https://github.com/zeek/zeek/wiki/Platform-Support-Policy

I've also added an entry to the calendar for macOS (Catalina, using the 
availability of images in Cirrus CI as a driver), and I'm putting 
together a PR (still a draft) for bringing our CI in line with what's in 
that page:


https://github.com/zeek/zeek/wiki/Platform-Support-Policy

Let me know your thoughts...

Thanks,
Christian
___
zeek-dev mailing list -- zeek-dev@lists.zeek.org
To unsubscribe send an email to zeek-dev-le...@lists.zeek.org

[Zeek-Dev] Re: Platform support policy

[Christian Kreibich]

On 10/22/20 1:40 AM, Robin Sommer wrote:

Want to start a Wiki page where we collect the pieces for our new
policy? Can link to those calendars from there.


Sure thing. I agree with your remaining comments, too.

Best,
Christian
___
zeek-dev mailing list -- zeek-dev@lists.zeek.org
To unsubscribe send an email to zeek-dev-le...@lists.zeek.org

[Zeek-Dev] Re: Platform support policy

[Amber Graner]

Can we also do a blog post and link this to the website? This way people
who are new can find it/discover it easier.

Thanks,
~Amber

On Thu, Oct 22, 2020 at 4:41 AM Robin Sommer  wrote:

> On Wed, Oct 21, 2020 at 14:14 -0700, Christian Kreibich wrote:
>
> > https://bit.ly/zeek-os-calendar-ical
> > https://bit.ly/zeek-os-calendar-google
>
> Cool, very nice!
>
> Want to start a Wiki page where we collect the pieces for our new
> policy? Can link to those calendars from there.
>
> > I think we've got this, too: when a new release starts, it should go into
> > CI, and when one drops off LTS EOL, it can go. What do you think?
>
> Yeah, though I think we'll need to discuss on per distribution basis
> what exactly the versions are that we want to support at any point of
> time (and hence have in CI), plus any additional assumptions we're
> making (e.g., requiring devtools-X on CentOS).
>
> That might be as easy as supporting anything currently in either
> release or LTS, but spelling it out in the terms of the corresponding
> distributions would be helpful to make sure everybody's on the same
> page (e.g., some phrasing of "on Ubuntu, we support the current
> release as well as any LTS release not EOL yet; and we assume just
> standard packages"). Could you give that a try on that Wiki page as
> well for those distros, and then we can send it around to the users'
> list to see if people can get behind it?
>
> One more OS to add is macOS. While nobody knows the deadlines there,
> we should record how far back we go in supporting previous versions,
> and what package management we're assuming for dependencies (Homebrew
> I suppose).
>
> Robin
>
> --
> Robin Sommer * Corelight, Inc. * ro...@corelight.com * www.corelight.com
> ___
> zeek-dev mailing list -- zeek-dev@lists.zeek.org
> To unsubscribe send an email to zeek-dev-le...@lists.zeek.org
>
-- 

*Amber Graner*
Director of Community
Corelight, Inc

828.582.9469

Schedule time on my calendar here. 



 * Ask me about how you can participate in the Zeek (formerly Bro)
community.
 * Remember - ZEEK AND YOU SHALL FIND!!
___
zeek-dev mailing list -- zeek-dev@lists.zeek.org
To unsubscribe send an email to zeek-dev-le...@lists.zeek.org

[Zeek-Dev] Re: Platform support policy

[Robin Sommer]

On Wed, Oct 21, 2020 at 14:14 -0700, Christian Kreibich wrote:

> https://bit.ly/zeek-os-calendar-ical
> https://bit.ly/zeek-os-calendar-google

Cool, very nice!

Want to start a Wiki page where we collect the pieces for our new
policy? Can link to those calendars from there.

> I think we've got this, too: when a new release starts, it should go into
> CI, and when one drops off LTS EOL, it can go. What do you think?

Yeah, though I think we'll need to discuss on per distribution basis
what exactly the versions are that we want to support at any point of
time (and hence have in CI), plus any additional assumptions we're
making (e.g., requiring devtools-X on CentOS).

That might be as easy as supporting anything currently in either
release or LTS, but spelling it out in the terms of the corresponding
distributions would be helpful to make sure everybody's on the same
page (e.g., some phrasing of "on Ubuntu, we support the current
release as well as any LTS release not EOL yet; and we assume just
standard packages"). Could you give that a try on that Wiki page as
well for those distros, and then we can send it around to the users'
list to see if people can get behind it?

One more OS to add is macOS. While nobody knows the deadlines there,
we should record how far back we go in supporting previous versions,
and what package management we're assuming for dependencies (Homebrew
I suppose).

Robin

-- 
Robin Sommer * Corelight, Inc. * ro...@corelight.com * www.corelight.com
___
zeek-dev mailing list -- zeek-dev@lists.zeek.org
To unsubscribe send an email to zeek-dev-le...@lists.zeek.org

[Zeek-Dev] Re: Platform support policy

[Christian Kreibich]

On 10/7/20 12:37 AM, Robin Sommer wrote:
Yes, that would be great. 


Okay, I've put one together:

https://bit.ly/zeek-os-calendar-ical
https://bit.ly/zeek-os-calendar-google

This includes CentOS, Debian, Fedora, FreeBSD, and Ubuntu.

I tried a few things and landed on one entry per release that starts on 
release date and ends on (LTS, when available) EOL. The benefit is that 
on any given day you see directly which releases are currently 
supported, and a click on any of the entries shows you start & end. The 
downside is that every day looks crowded, and it's a bit harder to see 
the starts/ends (week view brings it out okay though for me).



The other thing we'll need to do is define
the per distribution policies. You could add a 1st stab at that to the
calendar as well, or we can do it afterwards.


I think we've got this, too: when a new release starts, it should go 
into CI, and when one drops off LTS EOL, it can go. What do you think?


Thanks,
Christian
___
zeek-dev mailing list -- zeek-dev@lists.zeek.org
To unsubscribe send an email to zeek-dev-le...@lists.zeek.org

[Zeek-Dev] Re: Platform support policy

[Johanna Amann]

I just wanted to express the same sentiment - I like this :)

Johanna

On 7 Oct 2020, at 7:21, Christian Kreibich wrote:


On 10/5/20 4:08 AM, Robin Sommer wrote:

The advantage of this is that we won’t rely on having to specify
specific compiler versions, which isn’t well-defined (because 
things

also depend on libstdc++ version, system libs, etc.), but instead on
whether people can actually compile Zeek on the platforms they are
using.

A disadvantage is that we’ll need to spend the time to ensure our 
CI

setup keeps matching the policies, and gets updated as distribution
updates come out.


I like this a lot! At the end of the day, what matters for our builds 
is what the distros ship, and this covers that. Plus, it's not that 
hard to update the CI images to keep them current.


We could put together a release calendar to remind us when it's time 
to update CI. I took a quick look and couldn't immediately find one. 
I'd be happy to put one together.


Best,
Christian
___
zeek-dev mailing list -- zeek-dev@lists.zeek.org
To unsubscribe send an email to zeek-dev-le...@lists.zeek.org

___
zeek-dev mailing list -- zeek-dev@lists.zeek.org
To unsubscribe send an email to zeek-dev-le...@lists.zeek.org

[Zeek-Dev] Re: Platform support policy

[Robin Sommer]

On Tue, Oct 06, 2020 at 22:21 -0700, Christian Kreibich wrote:

> We could put together a release calendar to remind us when it's time to
> update CI. I took a quick look and couldn't immediately find one. I'd be
> happy to put one together.

Yes, that would be great. The other thing we'll need to do is define
the per distribution policies. You could add a 1st stab at that to the
calendar as well, or we can do it afterwards.

Robin

-- 
Robin Sommer * Corelight, Inc. * ro...@corelight.com * www.corelight.com
___
zeek-dev mailing list -- zeek-dev@lists.zeek.org
To unsubscribe send an email to zeek-dev-le...@lists.zeek.org

[Zeek-Dev] Re: Platform support policy

[Christian Kreibich]

On 10/5/20 4:08 AM, Robin Sommer wrote:

The advantage of this is that we won’t rely on having to specify
specific compiler versions, which isn’t well-defined (because things
also depend on libstdc++ version, system libs, etc.), but instead on
whether people can actually compile Zeek on the platforms they are
using.

A disadvantage is that we’ll need to spend the time to ensure our CI
setup keeps matching the policies, and gets updated as distribution
updates come out.


I like this a lot! At the end of the day, what matters for our builds is 
what the distros ship, and this covers that. Plus, it's not that hard to 
update the CI images to keep them current.


We could put together a release calendar to remind us when it's time to 
update CI. I took a quick look and couldn't immediately find one. I'd be 
happy to put one together.


Best,
Christian
___
zeek-dev mailing list -- zeek-dev@lists.zeek.org
To unsubscribe send an email to zeek-dev-le...@lists.zeek.org