[ANNOUNCE] Apache PredictionIO 0.11.0-incubating Release

The Apache PredictionIO team would like to announce the release of Apache PredictionIO 0.11.0-incubating. Release notes are here: https://github.com/apache/incubator-predictionio/blob/v0.11.0-incubating/RELEASE.md Apache PredictionIO (incubating) is an open source Machine Learning Server built

Re: Incubator Governance Change

On Sun, Apr 23, 2017 at 4:50 AM, Greg Stein wrote: > On Sat, Apr 22, 2017 at 7:46 PM, Roman Shaposhnik > wrote: >>... > >> I'm starting to wonder whether the real solution here should be along the >> lines >> of what a board would do to a TLP if its active

Re: [PROPOSAL] Superset Proposal for Apache Incubator

Hi Jeff, With the change to the proposal on the wiki, it now differs from the proposal text in the VOTE email. The reason we include the proposal text in the VOTE thread is because it represents the state of the proposal (which being a wiki page, is inherently mutable) at the time of the VOTE.

Re: Airflow voting on release artifacts

Would virtualenv help by avoiding the "Requirement already satisfied" complaints? On Tue, Apr 25, 2017 at 2:05 PM, Bolke de Bruin wrote: > Thank you thinking with us, that’s really appreciated. Unfortunately, many > of the assumptions from the Java world do not apply to the

Re: [PROPOSAL] Superset Proposal for Apache Incubator

Hi Raphael, what kind of numbers are you expecting to see? Max On Tue, Apr 25, 2017 at 12:59 PM, Raphael Bircher wrote: > Hi all > > There is no information about affiliation of the initial committers. The > only information is, that they are from Airbnb inc and

Re: Incubator Governance Change

> On Apr 25, 2017, at 9:06 PM, Roman Shaposhnik wrote: > > I honestly think its time for us to consider being more board like > around here at > IPMC. May be not exactly as strict as the board, but moving in that direction. > > After all, being a podling means being

Re: Airflow voting on release artifacts

> >3. There is no “separate” build script. Pip will just install a binary >(“wheel”) or uses the source package (as shown above). Both are used >interchangeable by users. We only distribute source packages at the >moment. > >@Alex: I have to think a little bit more about what you wrote, but it

Re: Incubator Governance Change

On Wed, Apr 26, 2017 at 5:47 AM, P. Taylor Goetz wrote: > ...I mostly agree, but would hesitate with the idea that a podling be > responsible for raising a red flag > when mentors are inactive. If the IPMC isn’t doing it’s job, that’s on us, > not the projects we incubate

Re: Incubator Governance Change

On Tue, Apr 25, 2017 at 8:47 PM, P. Taylor Goetz wrote: > >> On Apr 25, 2017, at 9:06 PM, Roman Shaposhnik wrote: >> >> I honestly think its time for us to consider being more board like >> around here at >> IPMC. May be not exactly as strict as the

Re: Incubator Governance Change

Continuing down the road of blaming each other for the problem is stupid. Look the personnel is already ready, willing, and available to do the real vetting. All the IPMC has to do is recognize them and integrate them. On Wed, Apr 26, 2017 at 1:37 AM, Bertrand Delacretaz <

Re: Incubator Governance Change

On Tue, Apr 25, 2017 at 12:50 AM, Pierre Smits wrote: > Now, we can argue that mentors have an obligation to vote on releases of an > incubating project first before the vote is taken to this ml. But that > could lead to unnecessary delays and frustration. > Having the

Re: [VOTE] Superset Proposal for Apache Incubator

+1 (binding) Thanks, Ashutosh On Mon, Apr 24, 2017 at 5:45 AM, Luke Han wrote: > +1 binding > > Love to see Superset to be new incubator project. > > > Best Regards! > - > > Luke Han > > On Sun, Apr 23, 2017 at 10:53 PM, Jeff Feng

Re: [VOTE] Superset Proposal for Apache Incubator

+1 binding > On Apr 25, 2017, at 12:48 PM, moon soo Lee wrote: > > +1 (non-binding) > > On Tue, Apr 25, 2017 at 11:49 AM Ashutosh Chauhan > wrote: > >> +1 (binding) >> >> Thanks, >> Ashutosh >> >> On Mon, Apr 24, 2017 at 5:45 AM, Luke Han

Re: [VOTE] Superset Proposal for Apache Incubator

+1 (binding) On 4/25/17, 1:27 PM, "Julian Hyde" wrote: +1 binding > On Apr 25, 2017, at 12:48 PM, moon soo Lee wrote: > > +1 (non-binding) > > On Tue, Apr 25, 2017 at 11:49 AM Ashutosh Chauhan > wrote:

Re: [VOTE] Superset Proposal for Apache Incubator

+1 (binding) On Tue, Apr 25, 2017 at 4:52 PM, Jitendra Pandey wrote: > +1 (binding) > > On 4/25/17, 1:27 PM, "Julian Hyde" wrote: > > +1 binding > > > On Apr 25, 2017, at 12:48 PM, moon soo Lee wrote: > > > > +1

Re: Airflow voting on release artifacts

Thank you thinking with us, that’s really appreciated. Unfortunately, many of the assumptions from the Java world do not apply to the Python world: Version information inside the artefact needs to be in sync with the external filename. Examples: 1. Plain rename of the tar ball bolke$ pip

Re: [VOTE] Superset Proposal for Apache Incubator

+1 (non-binding) On Tue, Apr 25, 2017 at 11:49 AM Ashutosh Chauhan wrote: > +1 (binding) > > Thanks, > Ashutosh > > On Mon, Apr 24, 2017 at 5:45 AM, Luke Han wrote: > > > +1 binding > > > > Love to see Superset to be new incubator project. > > > > > >

Re: [PROPOSAL] Superset Proposal for Apache Incubator

Hi all There is no information about affiliation of the initial committers. The only information is, that they are from Airbnb inc and Hortonworks. But there are no numbers. Regards Raphael Am .04.2017, 09:17 Uhr, schrieb Jeff Feng : Thanks John and Max - I have

Re: [PROPOSAL] Superset Proposal for Apache Incubator

"Airbnb will submit a Software Grant Agreement (SGA) as Superset joins the incubator." Should I add this sentence in the proposal? Max On Mon, Apr 24, 2017 at 5:48 AM, John D. Ament wrote: > I missed this discussion. In your IP section, you list out: > > == Source and

Re: Airflow voting on release artifacts

Hi John, Typically one handles a “release candidate” equal to a release, except for the fact that it hasn’t been fully tested and reviewed yet. In case everyone (all entities) is satisfied with the RC it is then just rebranded to Release. Unfortunately, in the python ecosystem the version

Re: Airflow voting on release artifacts

Hi, On Mon, Apr 24, 2017 at 10:18 PM, Chris Riccomini wrote: > ...Hitesh recently raised the issue that the artifact that passes the vote > MUST be the one that we actually release... Yes in terms of having the same binary digests and signatures, but renaming the files is

Re: [PROPOSAL] Superset Proposal for Apache Incubator

Thanks John and Max - I have updated the proposal wiki to reflect this update. It now reads: Source and Intellectual Property Submission Plan Airbnb will submit a Software Grant Agreement (SGA) as Superset joins the incubator. We do not expect any complications for the submission of the

Re: Incubator Governance Change

On Tue, Apr 25, 2017 at 9:50 AM, Pierre Smits wrote: > ...we can argue that mentors have an obligation to vote on releases of an > incubating project first before the vote is taken to this ml... Mentors not voting on releases gives a very bad signal to me as to their

Re: Airflow voting on release artifacts

Hi Bertrand, > On 25 Apr 2017, at 09:04, Bertrand Delacretaz > wrote: > > Hi, > > On Mon, Apr 24, 2017 at 10:18 PM, Chris Riccomini > wrote: >> ...Hitesh recently raised the issue that the artifact that passes the vote >> MUST be the one

Re: Airflow voting on release artifacts

We have a similar issue in Polygene, but the internal version is simply the expected version, say 1.2.3 and the RC has the different file name. No packagers will ever get the -RC named artifact and no confusion is among community members as they are aware of this. IF the RC passes, then the rename

Re: Airflow voting on release artifacts

Hi Niclas, Is this Java or Python? I can only find Java for Polygene. Furthermore, how do you manage this you repository? Do you have the release already set in one of your files, e.g. something like this: https://github.com/apache/incubator-airflow/blob/v1-8-test/airflow/version.py

Re: View archive on podling private@ list

Niclas, All of the access rules are based on LDAP now. I've updated the guides recently to reflect that rosters are maintained via whimsy, and not via the XML files. To setup weex's permissions go to https://whimsy.apache.org/roster/ppmc/weex and add additional committers to the PPMC. I have a

Re: Incubator Governance Change

On Tue, Apr 25, 2017 at 3:56 AM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > On Tue, Apr 25, 2017 at 9:50 AM, Pierre Smits > wrote: > > ...we can argue that mentors have an obligation to vote on releases of an > > incubating project first before the vote is

Re: Airflow voting on release artifacts

I'll point out that this is a great conversation and set of questions to have with your mentors first, the IPMC later if they didn't respond/give you a clear path forward. Did you engage with them? I personally hate seeing rc's being put forward to the incubator. Most of us use git these days,

Re: Airflow voting on release artifacts

It is Java, but we have version references internally in all kinds of places. So, what happens is that the build creates the "expected final release", say "1.2.3" and sets all internal references to that. But the tarball will be -RCx, which is voted upon. And then, as Bertrand suggested, a rename

Re: View archive on podling private@ list

ok, cool... On Tue, Apr 25, 2017 at 6:41 PM, John D. Ament wrote: > Niclas, > > All of the access rules are based on LDAP now. I've updated the guides > recently to reflect that rosters are maintained via whimsy, and not via the > XML files. To setup weex's permissions

Re: Incubator Governance Change

On Tue, Apr 25, 2017 at 12:46 PM, John D. Ament wrote: > On Tue, Apr 25, 2017 at 3:56 AM Bertrand Delacretaz < > bdelacre...@codeconsult.ch> wrote: >>... We want all podlings to be actively mentored, and if that doesn't >> happen they should look for new mentors to make

Re: Airflow voting on release artifacts

On 4/25/17, 1:43 AM, "Bolke de Bruin" wrote: >Hi Bertrand, > >> On 25 Apr 2017, at 09:04, Bertrand Delacretaz >> wrote: >> >> Hi, >> >> On Mon, Apr 24, 2017 at 10:18 PM, Chris Riccomini >> wrote: >>> ...Hitesh recently