Re: [VOTE] Move Apache Metron to the Apache Attic and Dissolve PMC

+1 > > > On Nov 16, 2020, at 5:19 PM, David Lyle wrote: > > > > +1 > > > >> On Mon, Nov 16, 2020 at 3:10 PM Michael Miklavcic < > >> michael.miklav...@gmail.com> wrote: > >> > >> +1 > >> > >>> On Mon, Nov 16

Re: [VOTE] Move Apache Metron to the Apache Attic and Dissolve PMC

+1 Just to be explicit about my support. On Mon, Nov 16, 2020 at 9:01 AM Justin Leet wrote: > Hi all, > > This is a vote thread to retire Metron to the Attic, and dissolve the PMC. > This follows a discussion thread on the dev list ([DISCUSS] Retire Metron > to the

[VOTE] Move Apache Metron to the Apache Attic and Dissolve PMC

Hi all, This is a vote thread to retire Metron to the Attic, and dissolve the PMC. This follows a discussion thread on the dev list ([DISCUSS] Retire Metron to the Attic

[DISCUSS] Retire Metron to the Attic

Hi all, I want to start a discussion in the community to consider retiring Metron to the Apache Attic and dissolve the project management committee. For anyone unaware, an overview is available at Apache Attic . In short, it's a way to provide a wind-down process for

Re: Development Activity has dropped to effectively 0, what should we do?

; > > > > > > > > > > > > > > > > > > > On Thu, Apr 16, 2020 at 4:34 PM Dima Kovalyov > > wrote: > > > > > - Dropping Ambari. > > > > > > I like the progress that Apache did with Ambar

Re: Development Activity has dropped to effectively 0, what should we do?

This is a bit off the top of my head, but I'd I agree with pretty much all of points on what's bringing a lot of overhead. There's probably also a worthwhile discussion about what value we're shooting for the project to provide to people that influences what stays/goes. Thinking out loud a bit

Re: Centos6 and Centos7 instructions

I believe you should just have to make a similar README to what's in the Centos6 dir. If you go to the site-book dir and run `mvn site`, you should be able to open the output in your browser and ensure that your changes are there. If I recall correctly, the intent was to eventually drop Centos6

Re: [DISCUSS] Next Release - Life After 0.7.1

dell > > > > wrote: > > > > > > > Both PR #1527 <https://github.com/apache/metron/pull/1527> and #1533 > > > > <https://github.com/apache/metron/pull/1533> are now merged into > > master. > > > > > > > > On Fri

Re: [DISCUSS] GeoLite database licensing change, master build broken…..

ndation cannot be that entity I would think. > > > > We may want to send this past Apache Legal? > > > > > > > > On January 13, 2020 at 17:22:21, Justin Leet (justinjl...@gmail.com) > > wrote: > > > > On the whole, I agree. I think the immediate foc

Re: [DISCUSS] GeoLite database licensing change, master build broken…..

gt; solution via the --geo_url option. See more details here - > > https://github.com/apache/metron/tree/master/metron-platform/metron-data-management#geolite2-loader > > Anything else I'm missing? Probably worth some feedback from Justin Leet on > this as well. > > Thanks, > Mike &

Re: [DISCUSS] Next Release - Life After 0.7.1

//github.com/apache/metron/pull/1533 > >- https://github.com/apache/metron/pull/1527 > > > > Being towards the end of the year, people are going to be on holiday. It > > would be great if we could focus on reducing scope and getting a release > > cut. > > > >

JUnit 5 PR merged into master

Hi all, The JUnit 5 migration PR has been merged to master. From this point forward, please use the newer interfaces and methods. There are plenty of examples through the code, and for more information, check out see https://junit.org/junit5/. Brief list of things to be aware of when writing

Re: [DISCUSS] Next Release - Life After 0.7.1

https://github.com/apache/metron/pull/1568 and https://github.com/apache/metron/pull/1554 are in master now. On Fri, Dec 6, 2019 at 7:16 PM Justin Leet wrote: > I'd like to throw https://github.com/apache/metron/pull/1552 on the pile. > Per https://issues.apache.org/jira/browse/LEGAL-4

Re: Discuss: Time to update bundled SOLR support?

Someone working more on the feature branch can correct me if I'm wrong, but I believe that's occurring as part of the general "Upgrade HDP version" branch, since that involves a lot of major upgrades to more supported versions of basically all the components. Specifically, it looks like it occurs

[ANNOUNCE] Apache Metron-bro-plugin-kafka release 0.3.0

Hi all, I’m pleased to announce the release of Metron 0.3.0! It's been a little while coming, but there's a good number of improvements and fixes, both around functionality and testing. Thanks to everyone who's contributing to and using the plugin! Details: The official release source code

[RESULT][VOTE] Metron-bro-plugin-kafka Release Candidate 0.3.0-RC3

The vote has passed. Including my +1, the voting was: 3 binding +1’s no 0’s no -1’s. I'll start working on the remainder of the release process and will notify the dev and users lists once completed.

Re: [VOTE] Metron-bro-plugin-kafka Release Candidate 0.3.0-RC2

Alright, I'd make another RC either this afternoon or early tomorrow. Thanks! On Thu, Oct 10, 2019 at 8:15 AM zeo...@gmail.com wrote: > From my perspective, yes > > Jon Zeolla > > On Thu, Oct 10, 2019, 7:24 AM Justin Leet wrote: > > > Are we at the point where we're

Re: [VOTE] Metron-bro-plugin-kafka Release Candidate 0.3.0-RC2

Are we at the point where we're comfortable spinning up another RC? On Thu, Oct 3, 2019 at 5:04 PM Justin Leet wrote: > The vote has failed. The voting was: > 2 -1’s (binding) > > A new RC will be created once we're satisfied the latest fix has resolved > issues. > > On T

Re: [VOTE] Metron-bro-plugin-kafka Release Candidate 0.3.0-RC2

er testing to add support for the git version / > > branch of the plugin to test was added during development. > > > > This feature however makes it impossible to run the docker testing suite > > against the signed src tarball for verification. > > > > I have created

[VOTE] Metron-bro-plugin-kafka Release Candidate 0.3.0-RC2

This is a call to vote on releasing Apache Metron-bro-plugin-kafka 0.3.0 The release candidate is available at: https://dist.apache.org/repos/dist/dev/metron/metron-bro-plugin-kafka/0.3.0-RC2/ Full list of changes in this release:

Re: [VOTE] Metron-bro-plugin-kafka Release Candidate 0.3.0-RC1

ould rather live with the possibility that there's a delay post vote or if we'd rather start next week. On Sun, Sep 29, 2019 at 12:47 PM zeo...@gmail.com wrote: > Justin Leet was running this release previously > > Jon Zeolla > > On Sun, Sep 29, 2019, 12:07 PM Otto Fowler > wrote: > > &

Re: PRs done but Jiras not updated to reflect completion

; -s="tags/apache-metron_0.7.1-release" | grep "Justin Leet" Here's an unsorted, current list for anyone interested. Sidenote, I created https://jira.apache.org/jira/browse/METRON-2242 if anyone wants to improve the script's usability a bit. It's just to improve the scrip

Re: METRON-614 Developer Implications

The PR is now in master, so please update your PRs and branches accordingly. Justin On Fri, Aug 16, 2019 at 2:29 PM Justin Leet wrote: > Hi all, > > I will shortly be working on merging PR-1341 > <https://github.com/apache/metron/pull/1341> for METRON-614 > <https://jir

METRON-614 Developer Implications

Hi all, I will shortly be working on merging PR-1341 for METRON-614 . There are a couple of implications to this that developers should be aware of, in addition to changes documented in UPGRADING.md for

Re: [DISCUSS] Travis CI Build Time Limits

the first failed build that did all the > downloading, and then the cache will have been populated. > > On Wed, May 22, 2019 at 7:21 AM Nick Allen wrote: > > > > Justin Leet said > > <https://github.com/apache/metron/pull/1417#issuecomment-494464795> > >

Re: [DISCUSS] Build RPM/DEBs in Travis?

ink building the RPMs/DEBs as part of the Travis build is > > at least a small step in the right direction. > > > > > > On Wed, May 22, 2019 at 9:34 AM Justin Leet > wrote: > > > > > Theoretically, we didn't need to before there were both RPMs and DEBs > &g

Re: [DISCUSS] Build RPM/DEBs in Travis?

Theoretically, we didn't need to before there were both RPMs and DEBs since running dev up (which necessitates building those) is part of the build process. Since they've been split apart, I agree we probably should be building them, because nobody is going to run both unless they specifically

Re: Master build - failed due to Maven download fail

I saw the same thing on https://github.com/apache/metron/pull/1407, but bouncing Travis fixed it. Not sure if it's a connection issue or what, but it seems like we should be able to cache it to avoid downloading every time. On Mon, May 20, 2019 at 6:14 PM Michael Miklavcic <

[ANNOUNCE] Apache Metron release 0.7.1

Hi all, I’m pleased to announce the release of Metron 0.7.1! There's been a lot of work in put in for everything including fixes, improvements, documentation, refactoring, and discussion. Thanks to everyone who's contributed, and thanks to our users! There is a callout for users regarding the

Re: [RESULT][VOTE] Metron Release Candidate 0.7.1-RC2

r discussion on this point, and the release notes. > > > On May 13, 2019 at 22:34:58, Michael Miklavcic ( > michael.miklav...@gmail.com) > wrote: > >  > > On Mon, May 13, 2019, 8:28 PM Justin Leet wrote: > > > The vote has passed. Including my +1, the voting was: > &g

[RESULT][VOTE] Metron Release Candidate 0.7.1-RC2

The vote has passed. Including my +1, the voting was: 3 binding +1’s no 0’s no -1’s. I'll work on finishing out the release process tomorrow and will notify the dev and user lists.

Re: [VOTE] Metron Release Candidate 0.7.1-RC2

gt; +1 binding > > > > I validated the release tarball, ran the full test suite and validated > the > > CentOS 6 development environment. Everything looks solid. Let's ship it. > > > > On Wed, May 8, 2019 at 6:50 PM Justin Leet > wrote: > > &g

[VOTE] Metron Release Candidate 0.7.1-RC2

This is a call to vote on releasing Apache Metron 0.7.1 Full list of changes in this release: https://dist.apache.org/repos/dist/dev/metron/0.7.1-RC2/CHANGES The tag to be voted upon is: apache-metron_0.7.1-rc2 The source archives being voted upon can be found here:

Re: [DISCUSS] Metron Release - 0.7.1 next steps

he feature gap. > > > > > > https://github.com/apache/metron/pull/1398 > > > > > > On Thu, May 2, 2019 at 1:37 PM Michael Miklavcic < > > > michael.miklav...@gmail.com> wrote: > > > > > > > Here's the ticket I created to track it, which also refer

Re: [DISCUSS] Metron Release - 0.7.1 next steps

at feature has changed my mind about what to do about > it in the short term. I think we should move forward. > > Our vote landed 2-2. We are having a discussion about what to do with the > release. This is that discussion. > > On Thu, May 2, 2019, 10:52 AM Justin Leet wrote: >

Re: [DISCUSS] Metron Release - 0.7.1 next steps

t; > we successfully convinced you about the benefits. This is one of the > > > > reasons why this PR is going to be still huge after cleaning up the > > > commit > > > > history. After you having a look at the changes and the feature > itself, > > > >

Re: [DISCUSS] Full-dev role in PR testign

scuss threads on this as well if folks think they're still pertinent, but > I think we're pretty far removed now from that original point in time and > should just move forward with fresh perspectives. > > On Wed, May 1, 2019 at 9:21 AM Justin Leet wrote: > > > Re: the integration testing

Re: [DISCUSS] Full-dev role in PR testign

Re: the integration testing point above, a strategy I used recently to alleviate a similar problem was to exploit JUnit 5's extensions. I haven't played with this at all in Metron's code, so 1) Take this with a several grains of salt and 2) Feel encouraged to point out anything

[DISCUSS] Full-dev role in PR testign

Hi all, I wanted to start a discussion on something near and dear to all of our hearts: The role of full-dev in our testing cycle. Right now, we require all PRs to have spun up the full-dev environment and make sure that things flow through properly. In some cases, this is a necessity, and in

Re: [DISCUSS] Metron Release - 0.7.1 next steps

Short version: I'm in favor of #2 of 0.7.1 and #1 as a blocker for 0.8.0. #3 seems like a total waste of time and effort. The wall of text version: I agree this isn't "just the wrong thing shown", but for completely different reasons. To be extremely clear about what the problem is: Our "dev"

Re: [RESULT][VOTE] Metron Release Candidate 0.7.1-RC1

3. Find some other workable UI solution. >4. Other option? > > All things considered, I'm personally leaning towards #2 in the short-term, > but I think we should probably talk about this a bit before deciding what > RC2 should be. > > Best, > Mike > > > > >

[RESULT][VOTE] Metron Release Candidate 0.7.1-RC1

The vote has failed. The voting was: 2 binding +1’s (Justin, Nick) 2 non-binding -1’s (Otto, Mike) no 0’s As discussed in the release thread, any further RC's are pending the review and merge of PR#1360 (Parser aggregation UI implementation).

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

iklav...@gmail.com> wrote: > > > > > > > > > We're also not "incubator-metron" any longer. Do we require > any kind > > of > > > > > voting or +1 on that verification page to make corrections to > it? > > >

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

script ( https://github.com/apache/metron/pull/1394). This accounts for both of these changes, and should allow the script to be run normally. On Thu, Apr 25, 2019 at 3:22 PM Justin Leet wrote: > This is a call to vote on releasing Apache Metron 0.7.1 > > Full list of changes in thi

[VOTE] Metron Release Candidate 0.7.1-RC1

This is a call to vote on releasing Apache Metron 0.7.1 Full list of changes in this release: https://dist.apache.org/repos/dist/dev/metron/0.7.1-RC1/CHANGES The tag to be voted upon is: apache-metron_0.7.1-rc1 The source archives being voted upon can be found here:

Re: [DISCUSS] Next Release

METRON-2067Done 0.7.1 Michael > Miklavcic > METRON-2074Done 0.7.1 Michael > Miklavcic > METRON-2082Done 0.7.1 > Mohan > METRON-2006 Done 0.7.1

Re: [DISCUSS] Next Release

ate the "0.7.1" release version in JIRA. > > On Tue, Apr 23, 2019 at 1:41 PM Justin Leet wrote: > > > Absolutely. It'll probably be tomorrow before that gets into full swing. > > > > I don't believe we have a "0.7.1" release in Jira, and I (oddly

Re: [DISCUSS] Next Release

gt; > > >> again > > > >> today - https://issues.apache.org/jira/browse/METRON-1814 > > > >> > > > >> On Mon, Apr 15, 2019 at 2:22 PM Michael Miklavcic < > > > >> michael.miklav...@gmail.com> wrote: > > > >

Re: Problems with Dev deployment.

It's a guess, I bet removing files that were outright deleted still exist when constructing a new site-book. So older links to things like the codelab stuff still exist to link to, but aren't actually linked within the site-book. On Wed, Apr 10, 2019 at 12:08 PM Michael Miklavcic <

Re: [DISCUSS] Next Release

I'm in favor doing a release, pending the ticket Mike pointed out (and anything else someone comes up with). To the best of my knowledge, I think 0.7.1 is sufficient, but if someone comes up with something, it's not hard to pivot. On Wed, Mar 13, 2019, 13:08 Michael Miklavcic wrote: > I'd like

Re: [DISCUSS] Architecture documentation

Re: Labeling in Jira, I'm fine with having a be "Next + 1" from a release management perspective, but I'd still consider at least taking action on followup to be the relevant party's responsibility (implementer or whatever the case may be). We probably should have a more clear way to tag things

[DISCUSS] Charset PR merge effects

Hey all, I wanted to bring a bit of attention to a change and its effects before I push to master. PR#1341 Removes all uses of the default charset (which is platform dependent) and moves everything to UTF-8. This PR currently has a +1, but obviously

[ANNOUNCE] Apache Metron release 0.7.0

Hi all, I’m pleased to announce the release of Metron 0.7.0! There's been a lot of work on improvements, upgrades, discussion, and more. Thanks to everyone who's contributed, and thank you to our users. Details: The official release source code tarballs may be obtained at any of the mirrors

[RESULT][VOTE] Metron Release Candidate 0.7.0-RC1

The vote has passed. Including my +1, the voting was: 3 binding +1’s no 0’s no -1’s.

Re: [VOTE] Metron Release Candidate 0.7.0-RC1

ecting to dist.apache.org (dist.apache.org)|209.188.14.144|:443... > connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-12-11 15:18:50 ERROR 404: Not Found. > > [ERROR] Failed to download > https://dist.apache.org/repos/dist/dev/metron/0.7.0-RC1/KEYS > ```

[VOTE] Metron Release Candidate 0.7.0-RC1

This is a call to vote on releasing Apache Metron 0.7.0 Full list of changes in this release: https://dist.apache.org/repos/dist/dev/metron/0.7.0-RC1/CHANGES The tag to be voted upon is: apache-metron-0.7.0-rc1 The source archives being voted upon can be found here:

Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

"merge pull request" just offers a couple ways to commit directly within GitHub (plain merge of all commits, squash down into one commit, and rebase the PR and merge it). I don't recall it allowing you to enforce a format on the PRs for the commit (e.g. ( via ) closes apache/metron#), which

Please update Git Apache remote URL

If you haven't been watching this thread , the ASF remote for our Git instance has changed as part of a mandatory relocation. GitHub remote is the same and does not need any

Re: Authorization for Configuration

ch > pending this exact conversation winding down. > > Yup, understood. > > On Fri, Nov 30, 2018 at 7:36 AM Justin Leet wrote: > > > To start with, I'm thinking just the configuration, in particular > anything > > that touches the ConfigurationsUtils. I think for

Re: Metron Release 0.6.1 and/or Plugin release 0.3.0?

Bro Plugin is not impacted by the bug. We do > have > > a > > > > good amount of other Metron functionality to release though. I do > not > > > see > > > > a need to hold-up the release. > > > > > > > > --- > > >

Re: [VOTE] Metron-bro-plugin-kafka Release Candidate 0.3.0-RC1

( > > https://github.com/apache/metron-bro-plugin-kafka/commit/1dfc5239fae31a64026188109d1e346ce93d5c02#diff-361be0491d615952129ed5c8f39c9683L57 > ). > I've opened METRON-1910 and am testing a fix now. > > On Tue, Nov 27, 2018 at 2:36 PM Justin Leet wrote: > > > Thi

Re: Authorization for Configuration

or customizable) and the fine-grained integration with Ranger? > > > > Cheers, > > Ali > > > > On Wed, Nov 14, 2018 at 1:25 AM Justin Leet > wrote: > > > > > Hi all, > > > > > > Right now, our various configs can be modified by anyone wi

Re: [DISCUSS] Managing intermittent test failures

Well, since I just put out pretty much this same request on the dev thread, I'm +1. On Thu, Nov 29, 2018 at 10:26 AM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > Every now and then we see intermittent test failures, and rather than > sweeping them under the rug, we should have a

Re: Metron Release 0.6.1 and/or Plugin release 0.3.0?

ed, 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 forgot to pull master f

[VOTE] Metron-bro-plugin-kafka Release Candidate 0.3.0-RC1

This is a call to vote on releasing Apache Metron-bro-plugin-kafka 0.3.0 The release candidate is available at: https://dist.apache.org/repos/dist/dev/metron/metron-bro-plugin-kafka/0.3.0-RC1/ Full list of changes in this release:

Re: Metron Release 0.6.1 and/or Plugin release 0.3.0?

m and I'd like to keep it that way. :) > > https://github.com/apache/metron/pull/1276 > > 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 thought

Re: Metron Release 0.6.1 and/or Plugin release 0.3.0?

> > On Fri, Nov 16, 2018 at 10:08 AM Otto Fowler > wrote: > >> 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

Re: Metron Release 0.6.1 and/or Plugin release 0.3.0?

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 > >> future a

Re: [DISCUSS] Attribution and merging the Elasticsearch client migration

I took a look at this with Mike a bit, and it seems like it's pretty painful and without a clear way to avoid remerging conflicts. If the latest attempt doesn't work, I'm in favor of getting it in and just getting it down to as few commits as reasonably possible. On Thu, Nov 15, 2018 at 4:12 PM

[DISCUSS] Authorization for Configuration

Hi all, Sorry for the second copy of this email, I forgot the [DISCUSS] tag on the original. Otherwise, this has the same content. Right now, our various configs can be modified by anyone with access to the various scripts. I'd like to start a discussion around building out some authorization

Authorization for Configuration

Hi all, Right now, our various configs can be modified by anyone with access to the various scripts. I'd like to start a discussion around building out some authorization to be able to add some more fine grained controls around this. Other projects have some variants on how to accomplish this.

Re: [DISCUSS] Slack Channel Use

> > > > > > > > > > > > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/1aa85bc13d41e04a1f85c3100c2b803abe35d79b54062bbeaab83ace@%3Cdev.metron.apache.org%3E > > > > > > > > > > > > > >

Re: [DISCUSS] Deprecate split-join enrichment topology in favor of unified enrichment topology

+1, I haven't seen any case where the split-join topology isn't made obsolete by the unified topology. On Thu, Nov 1, 2018 at 6:17 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > Fellow Metronians, > > We've had the unified enrichment topology around for a number of months > now, it

Re: [DISCUSS] Slack Channel Use

If we want to push more discussion to the dev list, my obvious follow up question then is "What are we hoping to get out of Slack/irc/other interactive medium?". What discussion would we even want on there, if we can't have decisions and don't want usage/support? On Mon, Oct 22, 2018 at 12:44 PM

Re: Metron Release 0.6.1 and/or Plugin release 0.3.0?

o 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: > &g

Metron Release 0.6.1 and/or Plugin release 0.3.0?

Hi all, As you might recall from a prior discussion about release cadence, we were interested in initiating release threads near our board reports to see if we wanted to do releases or not. Additionally, the work is done to do two separate releases, so our options are releasing both, a single

Re: Bro plugin unit tests failing

Should we just put out a discuss for releasing in general, with this discussion noted? The outcome of the release cadence discussion was to put out a thread around each board report. I believe that's a few days from now, so it's good timing. As an aside, part of the post release activities for

Re: Bro plugin release process docs?

metron-bro-plugin-kafka and did a quick update > to the cwiki, but it could use some additional love, especially if we want > to split out the release processes generally. > > Jon > > On Wed, Oct 10, 2018 at 5:32 PM Justin Leet wrote: > > > Yeah, we need to update

Re: Bro plugin release process docs?

uld just make a 0.2 tag in the plugin repo, and > then > > >> release it in a more disjointed way. I know that's not super helpful > > since > > >> I don't have documentation for doing an apache release of the plugin > > other > > >> than hacking so

Re: [DISCUSS] Split apart releases for core Metron and the Bro plugin

pping from their process, what are they doing? I would > > assume > > > we'd want some sort of vote for the plugin version change as well. > > > > > > On Fri, Sep 7, 2018 at 10:15 AM Nick Allen wrote: > > > > > > > +1 for complete separation as yo

Re: [DISCUSS] Feature Branch guidance

our subsequent feature branches have gotten much better. We should take the > lessons learned along the way and formalize them as Casey is recommending > in our bylaws. I'll be following up with more specific thoughts on > language. > > Best, > Mike > > > On Fri, Sep 28, 20

Re: [DISCUSS] Feature Branch guidance

Ticket created: https://issues.apache.org/jira/browse/METRON-1799 I think that whole '/develop' is orphaned and can be dropped. On Fri, Sep 28, 2018 at 12:12 PM Casey Stella wrote: > I just noticed this, but googling "metron bylaws" yields > http://metron.apache.org/develop/bylaws.html which

Re: Metron dev environments moving to require Ansible 2.4+

I'm +1 on getting the PR merged in. I'd just follow up on this thread post merge to let everyone know they have to switch if they haven't. On Fri, Sep 28, 2018 at 9:32 AM zeo...@gmail.com wrote: > Hi All, > > As it currently sits, once METRON-1758 >

Re: [DISCUSS] Batch Profiler Feature Branch

t;> > >> > > > the > >> > >> > > > > seeding is performed? > >> > >> > > > > > >> > >> > > > > On Thu, Sep 20, 2018 at 10:26 AM Nick Allen < > >> n...@nickallen.org >

Re: [DISCUSS] Batch Profiler Feature Branch

ig from the CLI only. On the other hand, our > flat > > > file loaders are not typically seeding an existing structure. My > concern > > of > > > a local file profiler config stems from this stated goal: > > > > The goal would be to enable “profile seeding” w

Re: [DISCUSS] Batch Profiler Feature Branch

the Batch Profiler > without having to fuss with the input path. > > > > > > On Thu, Sep 20, 2018 at 9:46 AM Justin Leet wrote: > > > Re: > > > > > * You do not configure the Batch Profiler in Ambari. It is configured > > > and execut

[ANNOUNCE] Apache Metron release 0.6.0

Hi All, I’m happy to announce the release of Metron 0.6.0! There's a been a lot of great work everywhere on the project, and thanks to both everyone who contributed and our users. Details: The official release source code tarballs may be obtained at any of the mirrors listed in

Re: [MENTORS][DISCUSS] LICENSE and NOTICE likely outdated

ttp://www.apache.org/legal/release-policy.html#artifacts > > Mike > > > On Wed, Sep 12, 2018 at 10:29 AM Justin Leet > wrote: > > > Hi all, > > > > As mentioned on the release voting thread, there was a Slack discussion > > around our LICENSE

[MENTORS][DISCUSS] LICENSE and NOTICE likely outdated

Hi all, As mentioned on the release voting thread, there was a Slack discussion around our LICENSE and NOTICE file likely being outdated because they haven't been actively kept up to date since graduation. I suggested on the vote thread that we proceed with the current release, but consider it a

[RESULT][VOTE] Metron Release Candidate 0.6.0-RC1

The vote has passed. Including my +1, the voting was: 3 binding +1’s 1 non-binding +1’s no 0’s no -1’s.

Re: [VOTE] Metron Release Candidate 0.6.0-RC1

it a blocker for the next release. On Tue, Sep 11, 2018 at 6:09 PM James Sirota wrote: > +1 (binding) ran it up in full dev > > 07.09.2018, 06:30, "Justin Leet" : > > This is a call to vote on releasing Apache Metron 0.6.0 and the Bro-Kafka > > plugin 0.2.0 > > >

Re: [DISCUSS] Split apart releases for core Metron and the Bro plugin

vote for core Metron and a separate vote for plugin? > > > > Do we want try to get this separation done after the current release > cycle is over? > > +1 Let's wait for the next release to hash this out. > > > > > On Fri, Sep 7, 2018 at 10:27 AM Justin Lee

[DISCUSS] Split apart releases for core Metron and the Bro plugin

Right now, we tie together our main release and the Bro plugin, as seen in our 0.4.2 release https://archive.apache.org/dist/metron/0.4.2/ and the current RC. Other projects, e.g. NiFi , split apart these releases within their dist directories. In our case this

Re: [VOTE] Metron Release Candidate 0.6.0-RC1

necessary to update that file for this release, I can quick put out a PR, cancel the vote, and pretty easily put out a new RC with the script. Justin On Fri, Sep 7, 2018 at 9:30 AM Justin Leet wrote: > This is a call to vote on releasing Apache Metron 0.6.0 and the Bro-Kafka > plugin 0.2.0 &g

[VOTE] Metron Release Candidate 0.6.0-RC1

This is a call to vote on releasing Apache Metron 0.6.0 and the Bro-Kafka plugin 0.2.0 Full list of changes in this release: https://dist.apache.org/repos/dist/dev/metron/0.6.0-RC1/CHANGES https://dist.apache.org/repos/dist/dev/metron/0.6.0-RC1/CHANGES.bro-plugin The tags to be voted upon are:

Re: [DISCUSS] Feature branches post-merge

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

Re: [DISCUSS] Metron Release 0.6.0?

emselves, not bro-pkg, so I > submit a JIRA <https://bro-tracker.atlassian.net/browse/BIT-1985>. > > Jon > > > On Wed, Sep 5, 2018, 21:51 Justin Leet wrote: > > > Makes sense. Do we have any objection to just going to the artifact being > > 0.

Re: [DISCUSS] Metron Release 0.6.0?

led > that part, and I did the 0.1 tagging (as a prereq to this > < > https://github.com/apache/metron/commit/2e78df67c12a6fcad726551128e9753ad36d5ee9#diff-8e3bdd364219306b1fad91047208e6e4R30 > >) > last time the package was released. > > Jon > > On Wed, Sep 5

Re: [DISCUSS] Metron Release 0.6.0?

e new version string. I will > > throw together a JIRA and PR to do all this in case we decide to align > with > > x.y.z; we can trash it if we decide to stay with x.y. > > > > Jon > > > > On Wed, Sep 5, 2018 at 7:35 PM Justin Leet > wrote: > > > &g

Re: [DISCUSS] Metron Release 0.6.0?

to move to x.y.z, I can provide a PR to update the version to 0.2.0 unless someone else wants to volunteer. Otherwise, I'd like to release the artifact as apache-metron-bro-plugin-kafka_0.2.tar.gz Justin On Tue, Sep 4, 2018 at 12:15 PM Justin Leet wrote: > As an update, I'll be working on start

  1   2   3   >