Thanks Kellen, Pedro and Sheng for the feedback.
Kellen -
- Thanks for proposing 1.5 features. Kindly note them on the issue Sheng
created: https://github.com/apache/incubator-mxnet/issues/14619
- For your 2.0 proposals - can you please update them in the issue Sheng
created:
Hi Hagay,
Thanks for taking the initiative. The proposed scope in this thread is in
my opinion too large to fit in a single thread, so I'd suggest that we
start separate threads for each individual release item. To elaborate on
the reasons based on each individual item:
- For 1.4.1 which is in
Great initiative.
I would like to add the issue that tracks APIs that we would like to
break for 2.0 so we can take the chance to streamline and improve
customer facing code:
https://github.com/apache/incubator-mxnet/issues/9686
I would be happy to volunteer for 2.0 release with assistance from
Release breakdown makes sense to me Hagay. Thanks for initiating a
discussion.
Some features that I'm personally looking forward to that I hope can make
it into 1.5 (schedule permitting):
* TensorRT being integrated with the subgraph API
* VNNI MKLDNN support
* AMP training in MXNet
I like
Dear MXNet community,
I wanted to initiate a discussion about the plan and scope for the next
MXNet releases.
I suggest we focus on three releases, and get the process going in parallel:
(1) 1.4.1 - patch release on top of 1.4.0 to address some perf regressions
and memory leaks I am aware of,
