On Fri, Sep 14, 2018 at 13:45 -0500, Jonathan Siwek wrote:
> Anything else to worry about?
Are Jenkins and Coverity already pulling from GitHub?
I don't know if there's anything we can do on the old server to make
existing clones deal with the relocation more gracefully. I don't
wthink
On Fri, Sep 14, 2018 at 11:36 -0500, Jonathan Siwek wrote:
> I did some label tweaking and reduced some prefix names: "Component"
> -> "Area" and "Difficulty" -> "Pain".
Ok, thanks, makes sense.
Robin
--
Robin Sommer * Corelight, Inc. * ro...@corelight.com * www.corelight.com
On Fri, Sep 14, 2018 at 9:54 AM Robin Sommer wrote:
>
> real question here is if we want to switch repositories before or
> after 2.6?
Forgot to say that my sentiment is conditional -- if I find that it's
not disruptive/risky to the release process (e.g. whether I need to
make commits within bro
On Fri, Sep 14, 2018 at 9:54 AM Robin Sommer wrote:
>
> On Thu, Sep 13, 2018 at 19:39 -0500, Jon Siwek wrote:
>
> > A preview of what migrated issues will look like along with new labeling
> > scheme:
>
> The only thing I noticed is that the labels are
> quite long, making the list of tickets
On Thu, Sep 13, 2018 at 19:39 -0500, Jon Siwek wrote:
> A preview of what migrated issues will look like along with new labeling
> scheme:
Looks great, nice job. The only thing I noticed is that the labels are
quite long, making the list of tickets appear somewhat crowded. Could
we skip the
> On Sep 13, 2018, at 5:57 PM, John Althouse wrote:
>
> Could anyone update Bro on docker to include 2.5.5, 2.6-beta and master?
> https://hub.docker.com/r/broplatform/bro/tags/
>
> We use this with our internal trybro instance which is fantastic for quickly
> collaborating and testing
