> Shall we provide pip wheels for later release votes?
Apache projects generally do not provide binaries as "signed off"
release artifacts. That being said, binaries are commonly provided and
marked as "convenience binaries". Hence, no vote is necessary on them,
nor are they "official" releases.
> Shall we provide pip wheels for later release votes?
Apache projects generally do not provide binaries as "signed off"
release artifacts. That being said, binaries are commonly provided and
marked as "convenience binaries". Hence, no vote is necessary on them,
nor are they "official" releases.
Hi All,
The html page source is available at the link (view source, its all in a single
html file), if someone wants to make modifications I’ll be happy to help
integrate those changes and get the latest version published in the S3 bucket.
Whenever the final location of the nightly builds is
Thanks,
I believe that we have a CCLA between *Verizon Media* (was Yahoo) and
Apache. This however is a contribution from *Verizon* (the parent company)
and I don't think they've had a relationship with Apache. So they are
asking my assistance to get everything in place.
I believe they will have
Awesome work! It's really convenient to have this page.
Two cents:
(1) create a link on mxnet page to this one
(2) reorder the nightly as Tao suggested. Newest first.
On Mon, Jan 13, 2020 at 10:25 AM Skalicky, Sam
wrote:
> Hi All,
>
> The html page source is available at the link (view source,
I wonder if it is possible to just use the RFC mechanism for most API
change discussions.
Note that while API compatibility is important, having a clear RFC
mechanism would likely strike a balance between the need to evolve APIs
(e.g. 2.0) and stability of the project
TQ
On Mon, Jan 13, 2020 at
Dear Community,
Recently, there were some changes to C APIs that broke another downstream
project Horovod: https://github.com/apache/incubator-mxnet/issues/17292.
Since we do not have integration tests for downstream project, it becomes
critical for us to update APIs with extreme caution.
I
Isn't this something that gets selected through vcvars?
On Fri, Jan 10, 2020 at 6:46 PM shiwen hu wrote:
> use x64 host msvc. cmake -T host=x64
>
> Pedro Larroy 于2020年1月10日周五 上午7:28写道：
>
> > Is there a solution for this error in VS2017?
> >
> >
I am going to include Justin to get his take on this. Justin, does this
need to go to legal?
Thanks
Mike
On Mon, Jan 13, 2020 at 10:13 AM Gil Yehuda
wrote:
> Thanks,
> I believe that we have a CCLA between *Verizon Media* (was Yahoo) and
> Apache. This however is a contribution from
Hi Lin,
Thanks for the suggestions.
With respect to your proposal:
> (2) Any PR that contains API change should clearly state this in PR title.
> Otherwise, committer can reject the PR
I agree that PRs with API changes should be made more prominent. Another
mechanism that has already been
Thanks, it's working after updating to a 64 bit compiler.
https://github.com/apache/incubator-mxnet/pull/17206
On Mon, Jan 13, 2020 at 4:55 PM Pedro Larroy
wrote:
> Isn't this something that gets selected through vcvars?
>
> On Fri, Jan 10, 2020 at 6:46 PM shiwen hu wrote:
>
>> use x64 host
Dear MXNet community,
I'm happy to announce the results of the vote.
This vote passes with 13 +1 votes (5 binding) and no 0 or -1 votes.
+1 votes
* Zhi Zhang / binding
* Qing Lan / binding
* Markus Weimer / binding
* Haibin Lin / binding
* Jun Wu / binding
* Lin Yuan
* Lai Wei
* Xinyu Chen
*
12 matches
Mail list logo
