Hi community,
Thanks for the initiative from Sam (samskalicky@github), we already have a discussion thread [1] on github about the defects and bugs exposed in the 1.5.0 release. Shufan (juliusshufan@github) and I (TaoLv@github) would like to manage the release of 1.5.1. This will be our first debut on the release process, your comments are always valuable. Per the SemVer 2.0 [2], MXNet 1.5.1 will be a patch release which contains backwards-compatible fixes only. I have created a page on cwiki [3] to track the release process and moved the issues and PRs mentioned in the github discussion thread to the page. Here I would like to ask the community to: (1) Raise any other defect or regression you identified in the 1.5.0 release. Please file a github issue for it and note the issue number in this thread; (2) Please comment with one sentence for why you think the issue is critical and must have in the 1.5.1 release; (3) If the issue is already fixed on master branch or already have a PR WIP, please also note the fix commit id or PR number; (4) If the issue is still open and there is no PR WIP, please indicate whether you'd be willing to help it out; (5) Feel free to comment if any other suggestion for the release. I suggest to keep this thread open for one week to collect enough information and proposals before we decide the timeline for the release. So your timely response will be highly appreciated! PS: Sorry to say that even as a committer, this is the first time for me to manage a release. So it would be great if an experienced committer can help to guide the process. -tao [1] https://github.com/apache/incubator-mxnet/issues/15613 [2] https://semver.org/ [3] https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status
