I'm not aware of the bro plugin artifacts being used in any way.
Jon
On Thu, Sep 6, 2018, 10:59 Justin Leet wrote:
> Do we use the artifacts directly at all? Or is it through bro-pkg only?
>
> Also, It's very possible I'm making a mountain out of a molehill here, and
> if it's something that's
I'm also inclined to drop them. They're in master and only exist to
facilitate dev. It seems unlikely to be a common case where someone wants
to really dig through the actual feature branch history rather than what
ended up in master.
On Thu, Sep 6, 2018 at 1:49 PM Casey Stella wrote:
> I’d get
I’d get rid of them.
On Thu, Sep 6, 2018 at 13:42 Michael Miklavcic
wrote:
> What are we doing with feature branches once they're complete and merged
> into master? Is our expectation that we'll keep feature branches in
> perpetuity, or should we plan to do some house cleaning once they've been
What are we doing with feature branches once they're complete and merged
into master? Is our expectation that we'll keep feature branches in
perpetuity, or should we plan to do some house cleaning once they've been
merged? I did a quick check of NiFi and Kafka and don't see much by way of
feature
Do we use the artifacts directly at all? Or is it through bro-pkg only?
Also, It's very possible I'm making a mountain out of a molehill here, and
if it's something that's not particularly important, it might be worthwhile
to just stick with what we did last time, and just table this discussion
Either is fine with me. If it's x.y in some parts of the app I prefer to
keep it consistent throughout, but I'm also fine with lining up with
Apache/Metron where we can.
I also refreshed myself on why we avoided x.y.z initially and it was
actually for this exact reason, we wanted consistent
