[Bro-Dev] 2.5.1 release?

2017-05-12 Thread Robin Sommer
Some of us have been talking about doing a 2.5.1 maintainance release.
It has been suggested to divert from our normal route of picking just
important fixes and instead go ahead and include what's currently in
master, given that we actually don't have much new functionality in
there yet at this time. I just went through the CHANGES since 2.5 and
I can see snapshotting current master as 2.5.1 if folks here are fine
with doing a broader release (which will need a bit more testing than
just a bugfix update would). Any opinions?

(Note I wouldn't want to exclude just individual commits currently in
master from 2.5.1, as that gets messy quickly. I would say it's either
all of master right now, or we pick selected commits for a narrow
release as we did in the past).

Robin

-- 
Robin Sommer * ICSI/LBNL * ro...@icir.org * www.icir.org/robin
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev


Re: [Bro-Dev] 2.5.1 release?

2017-05-12 Thread Seth Hall

> On May 12, 2017, at 4:34 PM, Robin Sommer  wrote:
> 
>  I just went through the CHANGES since 2.5 and
> I can see snapshotting current master as 2.5.1 if folks here are fine
> with doing a broader release (which will need a bit more testing than
> just a bugfix update would). Any opinions?

I'd be fine with that.  I think master is quite stable right now anyway.

  .Seth

--
Seth Hall * Corelight, Inc * s...@corelight.com * www.corelight.com

___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev


Re: [Bro-Dev] 2.5.1 release?

2017-05-12 Thread Slagell, Adam J

On May 12, 2017, at 4:08 PM, Seth Hall 
mailto:s...@corelight.com>> wrote:

I'd be fine with that.  I think master is quite stable right now anyway.

Agreed.

My understanding is that we still have some stochastic tests that fail for 
timing issues, but not if run manually on master. Is that correct?

:Adam

--

Adam J. Slagell
Director, Cybersecurity & Networking Division
Chief Information Security Officer
National Center for Supercomputing Applications
University of Illinois at Urbana-Champaign
www.slagell.info

"Under the Illinois Freedom of Information Act (FOIA), any written 
communication to or from University employees regarding University business is 
a public record and may be subject to public disclosure."








___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev


Re: [Bro-Dev] 2.5.1 release?

2017-05-12 Thread Daniel Thayer
On 5/12/17 4:33 PM, Slagell, Adam J wrote:
>
>
> My understanding is that we still have some stochastic tests that fail
> for timing issues, but not if run manually on master. Is that correct?
>
> :Adam


Correct.  I haven't seen any failing tests recently
that indicate a real problem in the software.
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev


Re: [Bro-Dev] 2.5.1 release?

2017-05-12 Thread Slagell, Adam J


> On May 12, 2017, at 4:09 PM, Seth Hall  wrote:
> 
> I'd be fine with that.  I think master is quite stable right now anyway


I'm pretty sure Vlad is in agreement, but traveling today. I think Justin as 
well, but I should let him speak for himself. 
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev


Re: [Bro-Dev] 2.5.1 release?

2017-05-12 Thread Johanna Amann
Looking over Changes, there is nothing that I am especially concerned
about at a cursory glance.

Johanna

On Fri, May 12, 2017 at 05:08:51PM -0400, Seth Hall wrote:
> 
> > On May 12, 2017, at 4:34 PM, Robin Sommer  wrote:
> > 
> >  I just went through the CHANGES since 2.5 and
> > I can see snapshotting current master as 2.5.1 if folks here are fine
> > with doing a broader release (which will need a bit more testing than
> > just a bugfix update would). Any opinions?
> 
> I'd be fine with that.  I think master is quite stable right now anyway.
> 
>   .Seth
> 
> --
> Seth Hall * Corelight, Inc * s...@corelight.com * www.corelight.com
> 
> ___
> bro-dev mailing list
> bro-dev@bro.org
> http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
> 
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev


Re: [Bro-Dev] 2.5.1 release?

2017-05-12 Thread Azoff, Justin S

> On May 12, 2017, at 9:48 PM, Slagell, Adam J  wrote:
> 
> 
> 
>> On May 12, 2017, at 4:09 PM, Seth Hall  wrote:
>> 
>> I'd be fine with that.  I think master is quite stable right now anyway
> 
> 
> I'm pretty sure Vlad is in agreement, but traveling today. I think Justin as 
> well, but I should let him speak for himself. 

Yes.. I think the only other thing is that the pointer to the broctl submodule 
hasn't been updated lately.

There are bunch of fixes and a few new features in broctl master that would be 
nice to get out to people.

I just realized since the submodule hasn't been updated the broctl changes 
likely aren't running anywhere yet, including our dev/test clusters.  If the 
submodule pointer can be updated I can put master on our dev/test clusters and 
test everything out a bit more.



-- 
- Justin Azoff



___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev


Re: [Bro-Dev] 2.5.1 release?

2017-05-12 Thread Daniel Thayer
On 5/12/17 9:43 PM, Azoff, Justin S wrote:
>
>> On May 12, 2017, at 9:48 PM, Slagell, Adam J  wrote:
>>
>>
>>
>>> On May 12, 2017, at 4:09 PM, Seth Hall  wrote:
>>>
>>> I'd be fine with that.  I think master is quite stable right now anyway
>>
>>
>> I'm pretty sure Vlad is in agreement, but traveling today. I think Justin as 
>> well, but I should let him speak for himself.
>
> Yes.. I think the only other thing is that the pointer to the broctl 
> submodule hasn't been updated lately.
>
> There are bunch of fixes and a few new features in broctl master that would 
> be nice to get out to people.
>
> I just realized since the submodule hasn't been updated the broctl changes 
> likely aren't running anywhere yet, including our dev/test clusters.  If the 
> submodule pointer can be updated I can put master on our dev/test clusters 
> and test everything out a bit more.
>
>
>

The broctl pointer was updated recently (after that, we stopped
seeing jenkins broctl test failures).
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev


Re: [Bro-Dev] 2.5.1 release?

2017-05-12 Thread Vlad Grigorescu
Correct, I agree. I just did another review of CHANGES, and didn't spot
anything concerning. We'll look at upgrading our test cluster (and UIUC's
test cluster) to master.

On Fri, May 12, 2017 at 8:48 PM, Slagell, Adam J 
wrote:

>
>
> > On May 12, 2017, at 4:09 PM, Seth Hall  wrote:
> >
> > I'd be fine with that.  I think master is quite stable right now anyway
>
>
> I'm pretty sure Vlad is in agreement, but traveling today. I think Justin
> as well, but I should let him speak for himself.
> ___
> bro-dev mailing list
> bro-dev@bro.org
> http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
>
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev


Re: [Bro-Dev] 2.5.1 release?

2017-05-15 Thread Robin Sommer


On Sat, May 13, 2017 at 00:28 -0500, you wrote:

> We'll look at upgrading our test cluster (and UIUC's test cluster) to
> master.

Sounds good, let us know how that is going.

Robin

-- 
Robin Sommer * ICSI/LBNL * ro...@icir.org * www.icir.org/robin
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev


Re: [Bro-Dev] 2.5.1 release?

2017-05-16 Thread Hosom, Stephen M
Battelle's test cluster is currently on Master. I'll forward any issues that we 
have. 

-Original Message-
From: bro-dev-boun...@bro.org [mailto:bro-dev-boun...@bro.org] On Behalf Of 
Robin Sommer
Sent: Monday, May 15, 2017 11:18 AM
To: Vlad Grigorescu 
Cc: bro-dev@bro.org
Subject: Re: [Bro-Dev] 2.5.1 release?

Message received from outside the Battelle network. Carefully examine it before 
you open any links or attachments.



On Sat, May 13, 2017 at 00:28 -0500, you wrote:

> We'll look at upgrading our test cluster (and UIUC's test cluster) to 
> master.

Sounds good, let us know how that is going.

Robin

--
Robin Sommer * ICSI/LBNL * ro...@icir.org * www.icir.org/robin 
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev

___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev