| Category | Problem | Leads | Solution/comments |
| Tests | Improve test coverage | Sheng Zha, Kellen Sunderland, Bhavin Thaker. |
|
| Tests | Fix all disabled tests, flaky tests: https://github.com/apache/incubator-mxnet/issues/9412 | Sheng Zha, Steffen Rochel | |
| Tests | Optimize Nightly Tests (they take too long) | Meghna Baijal, Amol Lele | Move some to performance benchmarks |
| Processes | Ensure 2 weeks for release vote to begin (assuming only rc0) | Bhavin Thaker | Completed, added to the release checklist |
| Processes | Have a release czar that is the gatekeeper | Bhavin Thaker | Completed, added to the release checklist |
| Processes | Add keys of all committers to the Apache public keystore. | Bhavin Thaker | Get all Amazon committers to complete this action |
| Processes | As per Suneel Marthi, the committer sending the email should do all the release work and be the release lead. | Bhavin Thaker | Completed, added to the release checklist |
| Processes | All problems/fixes in release notes MUST have the PR link and a possible workaround if any | Bhavin Thaker | Completed, added to the release checklist |
| Processes | Decide list of Features planned for the release in advance | Sukwon | Completed, added to the release checklist |
| Processes | Every feature and bug fix must be in the release notes | Sukwon | Completed, added to the release checklist |
| Processes | All PRs must have better descriptions | Bhavin Thaker | Completed, reminder email sent to dev@; email thread subject = "[DISCUSSION] Adding labels to PRs" |
| Processes | PRs must be reviewed, no self merge | Bhavin Thaker | Completed, added to Development Processes |
| Processes | Automate the release process | Bhavin Thaker | Completed, New tasks will tracked in GitHub Issues. |
| Communication | We must decide on a single communication channel and all task owners must subscribe to email lists/slack channels. | Bhavin Thaker | Completed, There have been various discussions on dev@ on using dev@ and Slack@ but no clear consensus due to preferences being different for various contributors. For now, let the community decide what works best. |
| Licenses | Fix all license issues mentioned, check for others, get reviewed | Bhavin Thaker | Priority: RAT needs to be fixed. |
| Licenses | Automated RAT Check | Meghna Baijal | after licenses are clean - automate in unit tests by 17-Jan-2018. |
| Licenses | Automated license check for new files - verify | Meghna Baijal | RAT check should be sufficient. Request to enhance RAT instead of creating new project-specific checks. |
| Website | Define process for website release - add to release notes | Santhosh | Pending |
| Website | Decouple the website repo (?) | Santhosh | Pending |
| Website | Some issues need fixing (footer, remove 0.11.0.rc3 etc) | Santhosh | Pending |
| Docs | Review the Install Steps. Make available from readme. | Meghna Baijal | review and update the existing script |
| Docs | Define process for adding readme/tutorial for new features | Aaron | Completed |
| CI | Improve coverage in terms of instance types and versions | Bhavin Thaker | Completed. Marco has already added new instance types to the CI. See this wiki: Proposal: Auto Scaling |
| CI | Checklist for each webpage having steps to be tested in CI | Bhavin Thaker | Pending. |
| Blogs | Update process: Add permissions in advance, blog should be in HTML, etc. | Sukwon | This is AWS specific blog for Apache MXNet. |
| Open issues | Process to review, escalate open issues | Steffen Rochel | Completed?? Progress made by having a file of maintainers for various areas of MXNet Code. See email from Mu Li on dev@. |
| Open issues | Find a way to incentivize people to close issues | Steffen Rochel | |