Re: [RELEASE][VOTE] Release MXNet version 1.2.1.RC0

2018-06-22 Thread Sergio Fernández
Happy to help. On Fri, Jun 22, 2018, 21:40 Chris Olivier wrote: > thank you for the explanation > > On Fri, Jun 22, 2018 at 9:25 PM Sergio Fernández > wrote: > > > No, the result at dev@ it's fine. You just need 3 binding votes together > > in > > the two votes (dev@mxnet and general@incubator)

Re: [RELEASE][VOTE] Release MXNet version 1.2.1.RC0

2018-06-22 Thread Chris Olivier
thank you for the explanation On Fri, Jun 22, 2018 at 9:25 PM Sergio Fernández wrote: > No, the result at dev@ it's fine. You just need 3 binding votes together > in > the two votes (dev@mxnet and general@incubator). > > (sorry fot the other email I sent by mistake) > > On Fri, Jun 22, 2018, 21:

Re: [RELEASE][VOTE] Release MXNet version 1.2.1.RC0

2018-06-22 Thread Sergio Fernández
No, the result at dev@ it's fine. You just need 3 binding votes together in the two votes (dev@mxnet and general@incubator). (sorry fot the other email I sent by mistake) On Fri, Jun 22, 2018, 21:21 Anirudh wrote: > Does PMC in this page mean IPMC : > https://www.apache.org/foundation/voting.ht

Re: [RELEASE][VOTE] Release MXNet version 1.2.1.RC0

2018-06-22 Thread Sergio Fernández
I've replied in another thread to On Fri, Jun 22, 2018, 21:21 Anirudh wrote: > Does PMC in this page mean IPMC : > https://www.apache.org/foundation/voting.html#ReleaseVotes ? > Also, does this mean we need three IPMC votes to pass this release on dev > list ? > > Anirudh > > On Fri, Jun 22, 201

Re: [RELEASE][VOTE] Release MXNet version 1.2.1.RC0

2018-06-22 Thread Anirudh
Does PMC in this page mean IPMC : https://www.apache.org/foundation/voting.html#ReleaseVotes ? Also, does this mean we need three IPMC votes to pass this release on dev list ? Anirudh On Fri, Jun 22, 2018 at 9:15 PM, Sergio Fernández wrote: > Just wanted to refresh what > https://incubator.apac

Re: [RELEASE][VOTE] Release MXNet version 1.2.1.RC0

2018-06-22 Thread Chris Olivier
what does “binding” mean in this context? On Fri, Jun 22, 2018 at 9:15 PM Sergio Fernández wrote: > Just wanted to refresh what > https://incubator.apache.org/guides/ppmc.html#ppmc_and_binding_votes says: > "The only time when a PPMC member’s vote is binding is for the addition of > new PPMC mem

Re: [RELEASE][VOTE] Release MXNet version 1.2.1.RC0

2018-06-22 Thread Sergio Fernández
Just wanted to refresh what https://incubator.apache.org/guides/ppmc.html#ppmc_and_binding_votes says: "The only time when a PPMC member’s vote is binding is for the addition of new PPMC members and committers. Release votes are only binding to IPMC members.". So it's incorrect to mark as binding

RE: Project Proposal for fused CPU RNN OPs to the release 1.3

2018-06-22 Thread Zhao, Patric
Hello Steffen, Really thanks to look into our proposal. I totally understand your concern that the quality is the most important thing. We will pay much attention on it. Regarding RNN Ops, the new OP provides about 2-3X performance boost (the performance section of proposal). Most importantly,

Re: [RELEASE][VOTE] Release MXNet version 1.2.1.RC0

2018-06-22 Thread Chris Olivier
what do you mean? just curious. On Fri, Jun 22, 2018 at 4:44 PM Sergio Fernández wrote: > Please, notice PPMC votes are not binding. > > On Fri, Jun 22, 2018, 09:35 Anirudh wrote: > > > Hi all, > > > > Apologies for replying instead of sending out a new email. > > > > This vote has passed with

Re: [RELEASE][VOTE] Release MXNet version 1.2.1.RC0

2018-06-22 Thread Sergio Fernández
Please, notice PPMC votes are not binding. On Fri, Jun 22, 2018, 09:35 Anirudh wrote: > Hi all, > > Apologies for replying instead of sending out a new email. > > This vote has passed with 6 +1s: > > Binding: > Sandeep > Haibin > Indhu > > Non Binding: > Carin > Pedro > Lai > > I will proceed wi

Re: landing pages for the website

2018-06-22 Thread Steffen Rochel
Hi Aaron - support Mu's suggestion to add an ecosystems page to add links to MXNet related projects (gluon toolkits, mxnet model server, keras, onnx, sockeye etc) to promote the solutions in the MXNet ecosystem. What do you suggest as next steps? Steffen On Mon, Jun 11, 2018 at 5:19 PM Mu Li wrot

[RELEASE][VOTE] Release MXNet version 1.2.1.RC0

2018-06-22 Thread Anirudh
Hi all, Apologies for replying instead of sending out a new email. This vote has passed with 6 +1s: Binding: Sandeep Haibin Indhu Non Binding: Carin Pedro Lai I will proceed with the vote on general@. Thanks, Anirudh

Re: [VOTE] Release MXNet version 1.2.1.RC0 (Patch Release)

2018-06-22 Thread Anirudh
Hi all, Thanks a lot for checking the release. This vote has passed with: 6 +1s Binding: Sandeep Haibin Indhu Non Binding: Carin Pedro Lai Anirudh On Fri, Jun 22, 2018 at 8:00 AM, sandeep krishnamurthy < sandeep.krishn...@gmail.com> wrote: > +1 > > Lai (https://github.com/roywei) and myself

Re: C++ api issue labeling

2018-06-22 Thread Lin Yuan
I agree with Hagay. Using "Backend" as label makes it much easier to track. "C++" label only describes the language used in implementation, "Backend" better describes the nature of the work (let's assume we change the backend implementation from C++ to other languages in the future). Lin On Fri,

Re: [VOTE] Release MXNet version 1.2.1.RC0 (Patch Release)

2018-06-22 Thread sandeep krishnamurthy
+1 Lai (https://github.com/roywei) and myself tested with Keras-MXNet for CNN and RNN standard use cases, things are working as expected on CPU and GPU. Best, Sandeep On Thu, Jun 21, 2018 at 11:06 PM Anirudh wrote: > Hi all, > > Thanks for checking the release. We need one more binding +1. I w

Re: Project Proposal for fused CPU RNN OPs to the release 1.3

2018-06-22 Thread Steffen Rochel
Thanks Patric, appreciate your contributions. I looked at your design proposal. I'm missing any statements about validation of correctness and performance of the integrated solution. I would suggest to pay more attention to this aspect as we struggled in previously releases with the quality of the

Re: users@mxnet

2018-06-22 Thread Steffen Rochel
Thanks Isabel and Sergio for the feedback and evaluation criteria. Based on the discussion I see mixed views in the community. To summarize my suggestion: 1. Setup user@ list and staff with volunteers to respond to user requests. 2. Make changes based on feedback to grow the user list organically.

Re: users@mxnet

2018-06-22 Thread Sergio Fernández
Honestly, I'm quite surprised of the level of the reactions on this thread. When I started it, I just wanted to expand the community with a tool that, even some people consider it "old fashion", it has been proved to help many other Apache projects to foster their community in the past. I guess, u

Re: users@mxnet

2018-06-22 Thread Isabel Drost-Fromm
Am 20. Juni 2018 17:43:35 MESZ schrieb Steffen Rochel : >After a reasonable time like 6 months we can evaluate the adoption of >user@ >and effort to support and can make an informed, data driven decision >how to >proceed. In addition to adoption, I would add "amount of users converted to contr

Re: C++ api issue labeling

2018-06-22 Thread Hagay Lupesko
Thanks everyone for chiming in and clarifying. It seems that the "C++" label name is confusing for our community since it can be interpreted as both the CPP API and the backend... As an anecdote, this issue [1 ] is labeled as "C++" but is abou