Release plan - Apache MXNet (incubating) 1.0

I am starting the process to prepare for Apache MXNet (incubating) 1.0 Release. I have drafted the release notes to cover the tasks planned this release. A release candidate will be cut next week

[BUILD FAILED] Branch master build 620

Build for MXNet branch master has broken. Please view the build at https://builds.apache.org/job/incubator-mxnet/job/master/620/

Re: [DISCUSSION] Adding labels to PRs

As a complete noob here and someone without a JIRA account, it seems I can at least view JIRA issues (so a plus for regular users when it comes to release notes). And when it comes time to start contributing, I don't see having to create a JIRA account to be a big deal, especially if the

[BUILD FAILED] Branch master build 619

Build for MXNet branch master has broken. Please view the build at https://builds.apache.org/job/incubator-mxnet/job/master/619/

Re: [DISCUSSION] Adding labels to PRs

+1 for better [1] PR Titles. As suggested by Madan and use by Spark, the current PR template seems to be ignored by folks and so we may want to simplify it to: Q1. What changes were proposed in this pull request? Q2. How was this patch tested? +1 to either [2] Jira OR [3] PR labels. Bhavin

Re: [VOTE] A Separate CI System for Apache MXNet (incubating)

+1 for [1] (A setup separated from Apache Jenkins) On Mon, Nov 13, 2017 at 4:50 AM, sandeep krishnamurthy wrote: > +1 for [1] Jenkins (A setup separated from Apache Jenkins) - with > preferably AWS Code Build integration to reduce the size of infrastructure > we