Build for MXNet branch master has broken. Please view the build at
https://builds.apache.org/job/incubator-mxnet/job/master/378/
Side note:
There is no "we". The below should say something like "I would like to
propose...", or "As part of my work at , I would like to
propose..." if it's coming from a team at your day job and you don't want
to hog all the glory :)
If it truly is "we", then the email should end with the "we"
Thanks, Seb.
That is correct: I misunderstood the situation and thought that there
already was buy-in from within the pPMC, which is why this came across
as a foregone conclusion.
My apologies to all for inadvertently skewing the communications.
Kind regards,
Sally
- - -
Vice President Marketi
Thanks Naveen.
So the url in the website is wrong; install.html shouldn't have that
-incubating in the 0.11.0 directory name.
On Wed, Sep 13, 2017 at 11:33 AM, Naveen Swamy wrote:
> It's under the release directory here:
>
> https://dist.apache.org/repos/dist/release/incubator/mxnet/0.11.0/
>
It's under the release directory here:
https://dist.apache.org/repos/dist/release/incubator/mxnet/0.11.0/
https://dist.apache.org/repos/dist/release/incubator/mxnet/0.11.0/apache-mxnet-src-0.11.0-incubating.tar.gz
On Wed, Sep 13, 2017 at 11:13 AM, Henri Yandell wrote:
> The 0.11.0 release is m
Build for MXNet branch master has broken. Please view the build at
https://builds.apache.org/job/incubator-mxnet/job/master/374/
The 0.11.0 release is missing from here:
https://dist.apache.org/repos/dist/dev/incubator/mxnet/
Currently only the RCs are there.
We do have the download link:
* http://mxnet.apache.org takes you to:
* http://mxnet.apache.org/get_started/install.html takes you to:
*
https://www.apache.org/dyn/
I agree with Naveen. This is not a one-way door. We can refine and improve
the process as needed in the future.
I don't see this as case of who works harder (machines or humans). PRs
always involve a manual step. All we are saying is lets do the full
verification when someone reviewed the changes a
Clarifying as I think Isabel was too gentle :)
Before coming to Apache, there had been much talk of redoing the website,
perhaps via a dayjob contribution. I double checked at ApacheCon with Sally
that that was sane (corporate contribution of a website design).
The evolution of that conversation
Isabel, thanks for the feedback. I was following Sally's suggestions with
respect to wording and there seems to have been a miscommunication.
To clarify - The design is only a proposal and has not yet been adopted. It
has been posted on the /master subpage only for ease of access.
On Tue, Sep 12,
The current number of build steps for a successful build is around 30 each
requiring to run on a Jenkins executor(running on one instance), there are
plans to add additional tests(more build steps) for additional platforms
such as MAC OSX, IOT devices. I don't think it is practical nor necessary
to
I think this: >The pPMC would like to update the website.
is just to say that, the project's mentors reached out to the folks who
helped with the infra migration with a reminder about the website updates
that are needed.
I don't believe that a decision was made out of sight. Though I do fully
agr
12 matches
Mail list logo
