I agree, I would suggest moving forward with cutting an apache/metron RC.
Jon
On Wed, Dec 5, 2018 at 3:45 PM Nick Allen wrote:
> I would prefer to just go ahead with the release and not wait on an
> intermittent, integration test related JIRAs. Just wanting to see if there
> is support for get
I would prefer to just go ahead with the release and not wait on an
intermittent, integration test related JIRAs. Just wanting to see if there
is support for getting a RC out sooner rather than later.
On Tue, Dec 4, 2018 at 4:06 PM zeo...@gmail.com wrote:
> I agree that we should move forward w
I agree that we should move forward with the apache/metron 0.7.0 release.
If 0.3 gets finalized in time we can include it, but otherwise no big deal
not including it since the dev environment points to 0.1 which didn't have
the issue.
Jon
On Mon, Dec 3, 2018 at 5:09 PM Michael Miklavcic <
michael
I have one more intermittent failure to add to the list from a timeout in
the profiler integration tests.
https://issues.apache.org/jira/browse/METRON-1918
On Mon, Dec 3, 2018 at 2:54 PM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:
> fwiw, I have not been able to reproduce the integra
fwiw, I have not been able to reproduce the integration test failure that I
logged here - https://issues.apache.org/jira/browse/METRON-1851. Unless
anyone else has seen this, either locally or in Travis, I recommend we
close it out as unable to reproduce. If it does ever show up again, the
closed J
I'm inclined to do move forward with the core repo release. Having said
that, there's a few test bugs and such I'd like to see addressed, either
"won't fix" or preferably with PRs, before creating an RC (as noted earlier
in the thread). It's probably a good opportunity to ask again if there's
anyt
+1 Nick
On Mon, Dec 3, 2018 at 2:04 PM Nick Allen wrote:
> OK, well either way, I see no need to hold up Metron 0.6.1.
>
> On Mon, Dec 3, 2018 at 3:51 PM zeo...@gmail.com wrote:
>
> > I believe that 0.2.0 is impacted by the bug.
> >
> > Jon
> >
> > On Mon, Dec 3, 2018 at 3:50 PM Nick Allen wro
OK, well either way, I see no need to hold up Metron 0.6.1.
On Mon, Dec 3, 2018 at 3:51 PM zeo...@gmail.com wrote:
> I believe that 0.2.0 is impacted by the bug.
>
> Jon
>
> On Mon, Dec 3, 2018 at 3:50 PM Nick Allen wrote:
>
> > In light of this comment [1], I propose that we move forward with
I believe that 0.2.0 is impacted by the bug.
Jon
On Mon, Dec 3, 2018 at 3:50 PM Nick Allen wrote:
> In light of this comment [1], I propose that we move forward with another
> Metron release and forgo the Metron Bro Plugin 0.3.0 release until we can
> resolve METRON-1910 [2]. There is no need
In light of this comment [1], I propose that we move forward with another
Metron release and forgo the Metron Bro Plugin 0.3.0 release until we can
resolve METRON-1910 [2]. There is no need to rush the fix as the current
0.2.0 release of the Bro Plugin is not impacted by the bug. We do have a
good
There's a few issues I would like to see at least triaged and preferably
addressed prior to the release of the main repo. In Jira, we have a
"test-failures" label, that has a few things attached to it. If we know of
any other Jiras that should have this label attached, please do so and I'd
apprecia
A metron-bro-plugin-kafka 0.3 release is good to go from my side. Thanks
for all of the reviews Nick
On Wed, Nov 21, 2018 at 11:16 AM Nick Allen wrote:
> Ha. Yes, that definitely counts and makes a ton of sense. Thanks!
>
> On Wed, Nov 21, 2018 at 11:00 AM Justin Leet
> wrote:
>
> > Does "I
Ha. Yes, that definitely counts and makes a ton of sense. Thanks!
On Wed, Nov 21, 2018 at 11:00 AM Justin Leet wrote:
> Does "I forgot to pull master fresh before running the command" count as a
> reason?
>
> The missing Jiras are:
>
> METRON-1890 Metron Vagrant should disable audio (ottob
For metron-bro-plugin-kafka I'd like to get
https://github.com/apache/metron-bro-plugin-kafka/pull/19 into this release
as well, as it will be important to already exist in a release prior to
future releases of bro. It's a fairly trivial test-only change.
Jon
On Wed, Nov 21, 2018 at 11:00 AM Jus
Does "I forgot to pull master fresh before running the command" count as a
reason?
The missing Jiras are:
METRON-1890 Metron Vagrant should disable audio (ottobackwards) closes
apache/metron#1277
METRON-1874 Create a Parser Debugger (nickwallen) closes
apache/metron#1265
METRON-1880 U
Also, I'd like to get this one included in the release. This is really
annoying for people just wanting to try out the Profiler. And this was
'broken' after the last release, so there currently is no release with this
problem and I'd like to keep it that way. :)
https://github.com/apache/metron/
Any reason to not include everything in master at this point? There are 5
additional, *newer* commits beyond what you have here.
On Wed, Nov 21, 2018 at 10:11 AM Justin Leet wrote:
> Realized I'd never sent the updated list of Jiras. I changed the command
> slightly (to remove a clause I thoug
Realized I'd never sent the updated list of Jiras. I changed the command
slightly (to remove a clause I thought we'd already removed re: http, and
added the awk to remove dupes resulting from multiple commits for a single
Jira. I'll do a PR for these changes).
*apache/metron*
git log "master" "^t
I'm good with that release schedule, and using version 0.7.0 for the
apache/metron release.
I opened up METRON-1881 and have a branch ready to PR for the 0.3
plugin upgrade.
Jon
On Fri, Nov 16, 2018 at 10:08 AM Otto Fowler
wrote:
> Can you generate the jiras that would be included in the relea
Can you generate the jiras that would be included in the release?
On November 16, 2018 at 10:05:50, Justin Leet (justinjl...@gmail.com) wrote:
Given that we've had a couple major PRs (the ES client migration along with
the Angular upgrade stuff, and I'm sure others), I'd be in favor of
releasing
Given that we've had a couple major PRs (the ES client migration along with
the Angular upgrade stuff, and I'm sure others), I'd be in favor of
releasing both the plugin and the main repo.
I'd be in favor of doing something like:
metron-bro-plugin-kafka release 0.3.0
PR to update full dev
metron r
In my opinion metron-bro-plugin-kafka is ready for a release. Anything
else people would want to see? Once it gets released, I would like to
update full dev to use the newest version prior to any future metron
release (0.6.1 or whatever we choose).
Jon
On Wed, Nov 7, 2018 at 8:07 PM zeo...@gmai
So, about this release, anybody have time to review
apache/metron-bro-plugin-kafka#2 and apache/metron-bro-plugin-kafka#13?
Jon
On Wed, Oct 17, 2018 at 10:37 AM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:
> And I do think we will be ready to roll another Metron release in the near
>
And I do think we will be ready to roll another Metron release in the near
future as well.
On Wed, Oct 17, 2018 at 8:26 AM Justin Leet wrote:
> I tend to agree with Mike. I think we could do a release of the main
> project and get benefit, but I think skipping this cycle (especially since
> we h
I tend to agree with Mike. I think we could do a release of the main
project and get benefit, but I think skipping this cycle (especially since
we had a release last month) let's us get things like the ES client
migration in and settled and just generally make recommending a newer
version easier.
Migrating the ES client, refactoring parser bolt. There are some interface
changes in flight right now that I think would be beneficial to see in the
next release.
On Tue, Oct 16, 2018 at 2:01 PM Nick Allen wrote:
> I am in favor of a release for both.
>
> There are a lot of really useful bug fi
I am in favor of a release for both.
There are a lot of really useful bug fixes, management of pcap through
Ambari, more flexibility for configuring JAAS in Ambari, increased
Elasticsearch performance, the Syslog parser, and the Batch Profiler, among
others. I would be happy with calling it a 0.6.
I agree with a metron-bro-plugin-kafka release of 0.3.0 (0.3 in bro-pkg),
assuming we can get apache/metron-bro-plugin-kafka#2 in. I'm working on
adding travis to the metron-bro-plugin-kafka repo, but I'm not sure when I
will have enough time to finish my work there and wouldn't want to hold up
a
I'd be +1 on going with just the metron-bro-kafka-plugin release. It seems
like it's ready to go, and I think there are a few more things I'd like to
see get into our next Metron release so I'm good with holding off there.
Mike
On Tue, Oct 16, 2018 at 10:26 AM Justin Leet wrote:
> Hi all,
>
> A
29 matches
Mail list logo
