Re: [DISCUSS] Feature Branch guidance

+1 to both points. I'm in favor of keeping architectural changes limited in a feature branch. Architectural challenges beyond the scope of the branch should be brought back to the community for any necessary discussion. I don't think we've ever formalized what exactly closes out a feature branch

Re: [DISCUSS] Feature Branch guidance

+1 to those 2 bullet points Casey. And thanks Justin for adding the Jira for fixing the website. I can think of 2 good examples to borrow from recently that were submitted by community contributors. Shane Ardell brought up a discussion about migrating from Protractor to Cypress, and Tamas Fodor

Re: Metron dev environments moving to require Ansible 2.4+

Yeah, I thought we had more but maybe they where removed. Many places in *.md files referencing Ansible and versions too On September 28, 2018 at 11:45:14, zeo...@gmail.com (zeo...@gmail.com) wrote: Do you mean this ? It

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: [DISCUSS] Feature Branch guidance

I just noticed this, but googling "metron bylaws" yields http://metron.apache.org/develop/bylaws.html which is not our bylaws. Our bylaws are on https://cwiki.apache.org/confluence/display/METRON/Apache+Metron+Bylaws We should fix that. On Fri, Sep 28, 2018 at 12:02 PM Casey Stella wrote: >

[DISCUSS] Feature Branch guidance

Hi All, Given discussions about the current high-profile feature branch (Knox SSO), I thought it might be appropriate to have a conversation about what constitutes a feature branch and get some of this encoded in the community guidelines. Specifically, there was the request made that we split up

Re: Metron dev environments moving to require Ansible 2.4+

Do you mean this ? It was the only reference I could find on the wiki. All of the READMEs should be updated as a part of the PR, but feel free to provide your input if I missed anything. Jon On Fri, Sep 28, 2018 at 10:15 AM

Re: Metron dev environments moving to require Ansible 2.4+

We should make sure the non-source documentation is updated On September 28, 2018 at 09:32:52, zeo...@gmail.com (zeo...@gmail.com) wrote: Hi All, As it currently sits, once METRON-1758 is merged into the code base, Ansible 2.4 or later will be

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 >

Metron dev environments moving to require Ansible 2.4+

Hi All, As it currently sits, once METRON-1758 is merged into the code base, Ansible 2.4 or later will be required to use any of the Metron ansible playbooks. This is in contrast to the prior version requirements outlined in Metron documentation which

Re: [DISCUSS] Batch Profiler Feature Branch

Thanks for all the reviews and support. I have merged the feature branch into master. On Thu, Sep 27, 2018 at 2:41 PM James Sirota wrote: > +1 from me as well. great work > > 27.09.2018, 11:15, "Ryan Merriman" : > > +1 from me. Great work. > > > > On Thu, Sep 27, 2018 at 12:41 PM Justin Leet