[GitHub] [incubator-mxnet] ciyongch commented on issue #18641: Backporting recent mx.np changes to 1.7 branch
ciyongch commented on issue #18641: URL: https://github.com/apache/incubator-mxnet/issues/18641#issuecomment-653979033 Thanks @sxjscience and @BenjaminCHEN2016 for the great effort to backport the requested fixes to v1.7, now all of them were merged into v1.7.x via the PR https://github.com/apache/incubator-mxnet/pull/18653 and https://github.com/apache/incubator-mxnet/pull/18649. I will proceed with rc0 when the night build test passed. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-mxnet] ciyongch commented on issue #18641: Backporting recent mx.np changes to 1.7 branch
ciyongch commented on issue #18641: URL: https://github.com/apache/incubator-mxnet/issues/18641#issuecomment-652205754 Wow... can you help to evaluate how many PRs are related to enable this feature? Then we can decide the time needed and whether to include them or not? Thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-mxnet] ciyongch commented on issue #18641: Backporting recent mx.np changes to 1.7 branch
ciyongch commented on issue #18641: URL: https://github.com/apache/incubator-mxnet/issues/18641#issuecomment-652204662 Thanks @sxjscience for your prompt help on this. I've already ping the author for https://github.com/apache/incubator-mxnet/pull/18523, do you need any help for this PR? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-mxnet] ciyongch commented on issue #18641: Backporting recent mx.np changes to 1.7 branch
ciyongch commented on issue #18641: URL: https://github.com/apache/incubator-mxnet/issues/18641#issuecomment-652137950 Hi @sxjscience may I know if you're going to backport the above two PR into 1.7 as @szha suggested? We're waiting for them to be merged and tag rc0 now, thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-mxnet] ciyongch commented on issue #18641: Backporting recent mx.np changes to 1.7 branch
ciyongch commented on issue #18641: URL: https://github.com/apache/incubator-mxnet/issues/18641#issuecomment-651564244 Thanks @sandeep-krishnamurthy @szha , then let's take it as the experimental feature in v1.7 release. @sxjscience could you please help to backport these two PRs and tag me on the new PR? Then we'll move forward with rc0 tag and the rest of release process when they're get merged. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-mxnet] ciyongch commented on issue #18641: Backporting recent mx.np changes to 1.7 branch
ciyongch commented on issue #18641: URL: https://github.com/apache/incubator-mxnet/issues/18641#issuecomment-651487181 Hi @leezu, given the fact that the current numpy operator is still in active development, there could be more defects/bugs as including more new functionalities/features in v1.7. Thus it's uncertain about how longer it will take to backport these numpy bug fixes/features from master to v1.7, I suggest to mark numpy operator as experimental feature in v1.7 release, and decide a cut off day (for example 24h or 48h) to include the fixes that are available, and moving the 1.7 release process forward, what do you think? @szha @pengzhao-intel @TaoLv @ChaiBapchya @sandeep-krishnamurthy This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
