Re: [VOTE] Release Apache Groovy 2.4.4-incubating

On Mon, Jul 13, 2015 at 10:43 PM, Jochen Theodorou wrote: > ok, but there is no harm in listing allergens that are not actually in > there. So why can't we have a single NOTICE/LICENSE file that covers both > cases? Is it not possible to say something that the binary distribution will > additiona

[RESULT][VOTE] Release Sentry incubating version 1.5.1 (rc0)

Hi All, Voting for Sentry incubating release 1.5.1 is now closed. The release has passed with the following tally: Binding +1s: Justin Mclean, Jarek Jarcec Cecho, Arvind Prabhakar. Non binding +1s: Prasad Mujumdar, Lenni Kuff, Sravya Tirukkovalur A big thanks to everyone who voted! We'll cont

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

On 7/13/15, 10:43 PM, "Jochen Theodorou" wrote: >Am 14.07.2015 07:26, schrieb Alex Harui: >> >> >> On 7/13/15, 10:05 PM, "Jochen Theodorou" wrote: >>> >>> then source and binary distribution have to have different >>> NOTICE/LICENSE files? >> >> Yep, I think of it as the list of allergens in t

Re: [VOTE] Release of Apache Lens 2.2.0-beta-incubating

+1 (binding) On Sun, Jul 12, 2015 at 8:39 AM, Jaideep Dhok wrote: > Hello everyone, > > This is the call for vote for the following RC to be released as official > Apache Lens 2.2.0-beta-incubating release. This is our third release. > > Apache Lens provides an Unified Analytics interface. Lens

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Am 14.07.2015 07:26, schrieb Alex Harui: On 7/13/15, 10:05 PM, "Jochen Theodorou" wrote: then source and binary distribution have to have different NOTICE/LICENSE files? Yep, I think of it as the list of allergens in the package. If you use peanut oil to cook the raw ingredients, you’d be

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

On 7/13/15, 10:05 PM, "Jochen Theodorou" wrote: > >then source and binary distribution have to have different >NOTICE/LICENSE files? Yep, I think of it as the list of allergens in the package. If you use peanut oil to cook the raw ingredients, you’d better tell the consumer. -Alex

Re: Podling request: Gerrit

> This is pretty far from what the norm is, and is being proposed by a > podling, so I'd expect some skepticism. Other podlings, have proposed > similar workflows (albeit with extra problems.) and were not allowed > to retain that procedure. I think there's some confusion here about what the workf

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Am 13.07.2015 23:00, schrieb Justin Mclean: Hi, We don't bundle the source from any of those libraries true, but we do generate sources as part of our build using ANTLR and we do bundle the class files from the ANLTR and ASM projects in some of our jars and we do bundle the jars from some of

Re: Podling request: Gerrit

On Mon, Jul 13, 2015 at 9:38 PM, Ian Maxon wrote: >> This is a severe problem and needs to be rectified promptly. >> How are commits migrating from the external repository to the ASF repository? >> We typically end up missing provenance information that is important >> in blind mirroring of conten

Re: [VOTE] Release Sentry incubating version 1.5.1 (rc0)

+1 (binding, fwded from my vote on dev list) Regards, Arvind Prabhakar On Thu, Jul 9, 2015 at 6:07 PM, Shen, Guoquan wrote: > Hello IPMC, > We have passed the PPMC vote for Sentry incubator release 1.5.1(rc0) with > 3 +1 votes from > Lenni Kuff, Prasad Mujumdar and Sravya Tirukkovalur. We ask

Re: Podling request: Gerrit

> This is a severe problem and needs to be rectified promptly. > How are commits migrating from the external repository to the ASF repository? > We typically end up missing provenance information that is important > in blind mirroring of content. > There's no blind mirroring going on here. What we

Re: Podling request: Gerrit

To add onto Jochen's comments, even something lesser than a hosted Gerrit instance might suffice. The core issue for integrating our previous Git workflow is that, as I understand it, there's no way to have "robot" committers to ASF git. We previously had Gerrit acting on behalf of whoever submitte

Re: Podling request: Gerrit

IIRC, the problem with Gerrit workflow is that actually pushes into the repo are actually done by the bot. This runs against ASF's desire to keep push logs that actually make sense. The setup that you're describing (although ASCII art came broken via Gmail) seems to be addressing that very problem

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Hi, > What tool are you using to find the licenses that are not listed ? Noting special, just find + grep. I generally do something like this, piped to a couple of grep -v’s to remove noise where needed: find . -name "*.*" -exec grep “BSD" {} \; -print find . -name "*.*" -exec grep “GPL" {} \; -

Re: Podling request: Gerrit

On Mon, Jul 13, 2015 at 7:24 PM, Jochen Wiedmann wrote: > Hi, > > I am writing as one of the Mentors of the AsterixDB podling. > > It recently came to my attention, that there are, in fact, multiple > Git repositories, which are used by the project, one of them being > located externally of the AS

Podling request: Gerrit

Hi, I am writing as one of the Mentors of the AsterixDB podling. It recently came to my attention, that there are, in fact, multiple Git repositories, which are used by the project, one of them being located externally of the ASF. I understand the structure to be like this: +--+ C

Re: [VOTE] TinkerPop 3.0.0-incubating Release

Hi, +1 binding For the source releases I checked: - incubating in artefact name - signatures and hashes good - DISCLAIMER exists - LICENSE and NOTICE good - all source files have Apache headers - no unexpected binaries - Unable to compile form source as it require a very recent java version (1.8

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Le 13/07/15 23:21, Justin Mclean a écrit : > Hi, > >> - LICENSE : I can't find the normalize.css file. > See: > ./subprojects/groovy-docgenerator/src/main/resources/org/codehaus/groovy/tools/stylesheet.css > ./subprojects/groovy-groovydoc/src/main/resources/org/codehaus/groovy/tools/groovydoc/gstri

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Hi, > - LICENSE : I can't find the normalize.css file. See: ./subprojects/groovy-docgenerator/src/main/resources/org/codehaus/groovy/tools/stylesheet.css ./subprojects/groovy-groovydoc/src/main/resources/org/codehaus/groovy/tools/groovydoc/gstringTemplates/topLevel/stylesheet.css It contains thi

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Hi, > We don't bundle the source from any of those libraries true, but we do > generate sources as part of our build using ANTLR and we do bundle the class > files from the ANLTR and ASM projects in some of our jars and we do bundle > the jars from some of those projects in some of our binary z

Re: Incubating HiveMind

On Sat, Jul 11, 2015 at 8:41 PM, Edmond Kemokai wrote: > Thanks for the follow up Roman! > > I would start thinking of a new name, though the existing ASF project with > the same name is a retired one so I don't know if it will be possible to > simply take it up eventually. Good point. That said,

Re: [VOTE] Release Sentry incubating version 1.5.1 (rc0)

+1 binding * Signature and checksums are correct * Name correctly contains “-incubating” suffix * Verified top level files (LICENSE, DISCLAIMER, NOTICE) * I was not able to compile the archive with maven 3.0.5, I was getting dependency issues with some pentaho library. The issue goes away with ne

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

On Mon, Jul 13, 2015 at 7:27 AM, Emmanuel Lécharny wrote: >>> It *was* written a couple of hours ago: >> "Projects typically use http://people.apache.org/~${RM}/** or the newer /dev >> tree of the dist repository or the >> staging features of repository.apa

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Hi! first all, I'd like to say that between the last RC that I reviewed and this one Groovy team has made huge progress. You guys rock! That said, the IP hygiene is one of the biggest parts of the curriculum known as Incubator. For that reason, I can't thank Justin enough for his thorough review.

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Am 13.07.2015 16:25, schrieb Paul King: [...] For binary releases: - All are missing DISCLAIMER, LICENSE and NOTICE These are all in the meta-inf directory within all the produced jars but agreed should be in the root of the zips (already true for src zip) as well. I thought having hose in ME

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

On 13/07/2015 10:12 PM, Justin Mclean wrote: - NOTICE contains items that are not required (as they are not bundled) and it’s not in usual format - LICENSE also contains several licenses/items that are not bundled and so shouldn’t be included e.g. ANTLR 2, ASM 4, Hamcrest, JLine, JSR223, JUnit,

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Le 13/07/15 16:09, Cédric Champeau a écrit : > 2015-07-13 16:03 GMT+02:00 Emmanuel Lécharny : > >> Le 13/07/15 13:48, Daniel Gruno a écrit : >>> Where is this documentation? If it is stated anywhere that >>> people.apache.org is an acceptable place for RCs, it is clearly wrong >>> and needs fixing.

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Hi, my +1 (Binding), for the source package. Addressing Justin's issues : There *are* issues, but considering the security issue fixed in this release, I'd rather have this version out. - The build scripts are failing because there are Windows file (^M at the end of ech line). Removing them let

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

The 'alternative' is dist.apache.org which is the right place to put it, since it is revision controlled, which means we'll keep track of what exactly was voted on, even after it's been deleted or moved. With regards, Daniel. On 2015-07-13 16:03, Emmanuel Lécharny wrote: Le 13/07/15 13:48, Da

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

2015-07-13 16:03 GMT+02:00 Emmanuel Lécharny : > Le 13/07/15 13:48, Daniel Gruno a écrit : > > Where is this documentation? If it is stated anywhere that > > people.apache.org is an acceptable place for RCs, it is clearly wrong > > and needs fixing. > > It's not written, it's a common usage for al

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Le 13/07/15 13:48, Daniel Gruno a écrit : > Where is this documentation? If it is stated anywhere that > people.apache.org is an acceptable place for RCs, it is clearly wrong > and needs fixing. It's not written, it's a common usage for almost all of the projects, AFAICT. It's good to know that it

[VOTE] Release Apache NiFi 0.2.0-incubating

Hello The Apache NiFi PPMC has voted to release Apache NiFi 0.2.0-incubating. The vote was based on the release candidate and thread described below. We now request the IPMC to vote on this release. Here is the PPMC voting result: 0 +1 (IPMC binding) - IPMC we need your help to reach the requisit

Re: [VOTE] Release of Apache Lens 2.2.0-beta-incubating

Hi, +1 binding For the source release I checked: - release contains incubating - signatures and hashes correct - DISCLAIMER exits - LICENSE and NOTICE correct - All source files have Apache headers - No unexpected binaries in release - Can compile from source Minor issues: - Any reason why are t

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Hi, -1 (binding) as LICENSE and NOTICE have issues, included files which have Apache header when they are licensed under other terms, and binary connivence files are missing required files (i.e. DISCLAIMER, LICENSE and NOTICE) Note that the binary LICENSE and NOTICE file are very likely differe

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Changed. Thanks for pointing it out! With regards, Daniel. On 2015-07-13 13:51, Cédric Champeau wrote: Here: http://www.apache.org/dev/release.html#host-rc 2015-07-13 13:48 GMT+02:00 Daniel Gruno : Where is this documentation? If it is stated anywhere that people.apache.org is an acceptabl

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Here: http://www.apache.org/dev/release.html#host-rc 2015-07-13 13:48 GMT+02:00 Daniel Gruno : > Where is this documentation? If it is stated anywhere that > people.apache.org is an acceptable place for RCs, it is clearly wrong and > needs fixing. > > With regards, > Daniel. > > > On 2015-07-13

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Where is this documentation? If it is stated anywhere that people.apache.org is an acceptable place for RCs, it is clearly wrong and needs fixing. With regards, Daniel. On 2015-07-13 13:43, Gianmarco De Francisci Morales wrote: It would be good to update the piece of documentation that sugges

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

It would be good to update the piece of documentation that suggests to put RC on personal space on p.a.o. -- Gianmarco On 13 July 2015 at 13:55, Cédric Champeau wrote: > Right. Will make sure to use it next time. > > 2015-07-13 12:53 GMT+02:00 Daniel Gruno : > > > Hi Cédric, > > The whole point

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Right. Will make sure to use it next time. 2015-07-13 12:53 GMT+02:00 Daniel Gruno : > Hi Cédric, > The whole point of the /dev/ branch on dist is for putting release > candidates to be voted on. > Once a release is approved, it is then moved to the /release/ branch. > people.apache.org really sh

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Hi, > Consider people.a.o as a staging repo for those artifacts. Which is the wrong place to place release candidates and has been for several years. Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org F

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Hi Cédric, The whole point of the /dev/ branch on dist is for putting release candidates to be voted on. Once a release is approved, it is then moved to the /release/ branch. people.apache.org really should not be used for this, especially as that machine will probably disappear in the not-too-

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

No particular reason but avoiding putting on "dist" artifacts that maybe downvoted, so the idea is to put the artifacts there once they've been voted. Consider people.a.o as a staging repo for those artifacts. 2015-07-13 12:46 GMT+02:00 Justin Mclean : > HI, > > >> The artifacts to be voted on ar

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

HI, >> The artifacts to be voted on are located here: >> http://people.apache.org/~cchampeau/groovy/ Is there any reason the artefacts are not available here: [1] https://dist.apache.org/repos/dist/dev/incubator/groovy Thanks, Justin 1. http://www.apache.org/dev/release.html#host-rc -

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

Argh, I forgot to vote over on the podling thread, so hey, I'll vote now! RAT check passed, signatures check out, tags check out, could build from source package. +1 binding, IPMC, mentor. A. On Mon, Jul 13, 2015 at 10:33 AM, Cédric Champeau wrote: > Hi all! > > The Apache Groovy PPMC has suc

Re: [VOTE] Release Apache SAMOA 0.3.0 (incubating)

+1 (binding) - Verified signature and checksums - Top level LICENSE seems fine. I'm not sure NOTICE is correct. Put the concerns below. Can other IPMC members share your thoughts? - No unexpected binaries - Able to build from source Notice says : Apache SAMOA (incubating) Copyright (C) 2014-

[VOTE] Release Apache Groovy 2.4.4-incubating

Hi all! The Apache Groovy PPMC has successfully voted the release of Apache Groovy 2.4.4-incubating [1], with 6 "+1" binding votes, one "+1" non binding, no "0" votes and one "-1" vote (see the explanation below). We are now asking the IPMC to vote it too. Since it is our first release under the A

Re: [VOTE] Release Apache SAMOA 0.3.0 (incubating)

Hi, We are missing one +1 vote from the incubator. Given that there was the weekend in between, I am going to extend the vote for one more day. Vote closes on July 14. Thanks, -- Gianmarco On 12 July 2015 at 00:38, Justin Mclean wrote: > Hi, > > +1 binding > > I checked: > - signatures and ha