Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

This vote passed with +1s (all binding) Billie Rinaldi Stian Soiland-Reyes Julian Hyde Justin Mclean John D. Ament Thanks, Casey On Mon, Nov 28, 2016 at 1:57 PM, Casey Stella wrote: > Hi Stian, > > We can clarify the licensing around Stix in the next release, no problem. >

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

Hi Stian, We can clarify the licensing around Stix in the next release, no problem. It is my understanding that it is 3-clause BSD. Casey On Wed, Nov 23, 2016 at 12:48 PM, Stian Soiland-Reyes wrote: > My vote: +1 (binding) > > +1 git tag matches src (commit >

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

Hi all, Thanks for pointing out the branding issues. The website is updated to refer to the apache release page. There is also a JIRA (with accompanying PR on github) to correct the branding

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

That's an issue. Want to let them know directly that their website needs fixing? On Nov 24, 2016 1:00 PM, "Justin Mclean" wrote: > Hi, > > > RE Justin - that's a potential issue, but is also how github works. > > It may be how GitHub works but it is IMO against

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

Hi, > RE Justin - that's a potential issue, but is also how github works. It may be how GitHub works but it is IMO against release policy especially as on their site they link to GitHub and not the Apache release area. Thanks, Justin

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

Hmm thought I voted +1 already RE Julian's concerns - the artifact includes "incubating" so that passes the incubator requirement. The requirement doesn't say that it has to include it in the pom's version. RE Justin - that's a potential issue, but is also how github works. Since they're doing

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

Hi, +1 binding I checked: - incubating in name - signatures and hashes good - DISCLAIMER exists - NOTICE good - LICENSE is OK but could be improved (see below) - Can compile from source For the LICENSE rather than pointing to a URL of the license for Stix please include the license in the

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

+1 (binding) but with reservations about branding. Downloaded, checked hashes, built using Oracle JDK 1.8 and maven-3.2.1 on Ubuntu Linux, ran apache-rat. I also re-read discussions about 0.2.0-RC2 [1] and 0.2.0-RC3 [2] releases. In README.md, the product is described as “Metron"; should be

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

My vote: +1 (binding) +1 git tag matches src (commit 7aea4ba35d1a931d72898bffd9725be3075fe8ca) (except site/ and .git*) +1 .asc signatures match, key in KEYS +0 .sha/.md5 hashes correct - could these have more conventional format and filenames? -0 Vote email didn't reference hash values or

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

+1 binding checksums and signature are correct builds from source and unit tests pass disclaimer is correct release consists of source code and matches tag contents license and notice notes: - The Chef copyright in NOTICE is good, but the files copied directly from Bento should not have ASF

[VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1

This is a call to vote on releasing Apache Metron 0.3.0-RC1 incubating Full list of changes in this release: https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. 0-RC1-incubating/CHANGES The tag/commit to be voted upon is apache-metron-0.3.0-rc1-incubating: