Thanks Anthony,
so that's where the notion "gradlew doesn't work on Windows" comes from.
Makes more sense now. But I don't think that is just as practical for Weex
as it is for BigTop.
On Sat, May 6, 2017 at 3:10 AM, Anthony Baker wrote:
>
> > On May 5, 2017, at 4:27 AM, sospartan wrote:
> >
>
Apache SystemML has been under incubation since November 2015 and so far
the project has accomplished 5 official Apache Releases, voted 4 new
committers/PPMC members and has welcomed a new mentor. The community also
continues to evangelize the project at universities, blog posts, public
webcasts as
Sigh, that was meant to be signed:
Cheers,
Chris
On Fri, May 5, 2017 at 1:44 PM, Chris Riccomini
wrote:
> Hello Incubator PMC’ers,
>
> The Apache Airflow community has voted and approved the proposal to
> release Apache Airflow 1.8.1 (incubating) based on 1.8.1 Release Candidate
> 2. We now kin
Hello Incubator PMC’ers,
The Apache Airflow community has voted and approved the proposal to release
Apache Airflow 1.8.1 (incubating) based on 1.8.1 Release Candidate 2. We
now kindly request the Incubator PMC members to review and vote on this
incubator release. If the vote is successful we will
> On May 5, 2017, at 4:27 AM, sospartan wrote:
>
> I'll remove whole playground sample app from artifacts innext release. So
> #7 would be a problem anymore.
> As the gradle wrapper will be removed too. I'll suggest use installed
> gradle to create that. These will be put in new "how to build fr
Hi John,
Can you please look at my response and advise?
-Arvind--- Arvind Surve | Spark Technology Center |
http://www.spark.tc/
From: Arvind Surve
To: "general@incubator.apache.org" ; John D.
Ament
Sent: Wednesday, May 3, 2017 8:48 PM
Subject: Re: [VOTE] Apache SystemML 0.
Hi -
Anyone else interested in mentoring?
Regards,
Dave
Sent from my iPhone
> On May 1, 2017, at 4:55 PM, Dave Fisher wrote:
>
> Hi -
>
> I had a discussion with Joe and another gentleman involved in Pulsar.
>
> They asked how long incubation takes. I answered that it depends. We reviewed
I'll remove whole playground sample app from artifacts innext release. So
#7 would be a problem anymore.
As the gradle wrapper will be removed too. I'll suggest use installed
gradle to create that. These will be put in new "how to build from source"
doc in root folder.
Pierre Smits 于2017年5月5日 周五下午6
I forgot to address in my conclusion aspect #7 (classes.jar).
This seems to be quite the issue, as I could not find a license associated
with it when I did the cursory review. Nor could I find in the proposal
anything more than a single reference. My question(s):
- where does this originate fr
Hi All,
To understand part of the problem correctly, in currently proposed release
there are many compiled components (jar files)that aren't allowed to be
included
> clr% find . -name "*.jar"
1. > ./android/playground/gradle/wrapper/gradle-wrapper.jar
2. > ./android/sdk/gradle/wrapper/
Thanks John for the feedback!
It is reasonable that the LICENSE and NOTICE files for src and binary
tarball should be in separate locations.
Yes, our release with rpm package has the same contents as binary tarball.
11 matches
Mail list logo
