Okay, thanks for elaborating. I definitely see your point there and we
definitely don't want these changes to pile up.
I don't feel strongly about this and won't stand in the way, I just want to
express my concern that this could lead to people having to touch all
language interfaces although
Marco,
Qing and I are working together on this. The idea is that we fail the build
if there is a operator change on the backend and have not synced to the
Scala API. We want to catch this before breaking the user's code which will
be a pretty bad experience.
On Tue, Jun 19, 2018 at 11:54 AM,
Hi Qing,
thank you for working on improving the compatibility of our APIs!
Your linked proposal does not describe the mentioned FILEHASH. Could you
elaborate a bit? Would this be a hash of the entire file, some hash created
based on the signature of the underlying C++ methods or maybe a
Hi all,
I am one of the maintainer for MXNet Scala package. Currently I am building up
a hash-check system on the generated API through C. The PR is in this URL:
https://github.com/apache/incubator-mxnet/pull/11239
A file named FILEHASH will be added to the Scala that created the MD5 string of
Jim,
Earlier on the thread you suggested to clarify and expand on the usage of a
user@ mailing list and how it is useful for a project.
It may be helpful for the community to learn a bit more about it. Could you
expand and/or share relevant links and examples?
Thank you,
Hagay
On Tue, Jun 19,
Just so we are clear: building and fostering a community takes effort. Either
it is something important to the project, or it's not.
My assumption is that It Is.
> On Jun 18, 2018, at 8:59 PM, YiZhi Liu wrote:
>
> I am personally not a big fan of mailing list but agree with Thomas
> that we
Welcome Jim. Great to have you in the project.
On Mon, Jun 18, 2018 at 10:51 PM Steffen Rochel
wrote:
> Welcome Jim, appreciating your support.
> Steffen
>
> On Mon, Jun 18, 2018 at 3:14 PM Naveen Swamy wrote:
>
> > Hi All,
> >
> > I am excited to announce that we have an additional mentor
