[BUILD FAILED] Branch master build 611

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

[BUILD FAILED] Branch master build 608

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

[BUILD FAILED] Branch master build 609

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

[RESULT][VOTE] Release Apache MXNet (incubating) Version 0.12.1.rc0

Hi All, The vote for releasing Apache MXNet (incubating) 0.12.1 RC0 passed with the following result - +1 binding - Chris Olivier - Sebastian - Indhu Bharathi There was no -1 and 0 Vote thread

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

+1 for [1] Jenkins (A setup separated from Apache Jenkins) - with various plugins. Bhavin Thaker. On Fri, Nov 10, 2017 at 11:39 AM, Madan Jampani wrote: > +1 for (1) > > On Thu, Nov 9, 2017 at 4:41 PM, Meghna Baijal > wrote: > > > Hi All, >

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

+1 for (1) On Thu, Nov 9, 2017 at 4:41 PM, Meghna Baijal wrote: > Hi All, > A need has been identified for MXNet’s CI/CD setup to move away from the > Apache Jenkins Service. Over the past few days there has been active > discussion on the necessary and advanced

Re: [DISCUSSION] Adding labels to PRs

Option 2 works for us over in REEF. We are a bit (too) religious about it [0], but it creates really nice commit messages[1]. We require each commit message to start with a one line summary which names the JIRA in brackets and describes the change, e.g. `[REEF-1234] Added integration with mxnet`.

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

+1 for 1) (binding) On 10.11.2017 10:30, kellen sunderland wrote: +1 for 1 (non-binding) On Fri, Nov 10, 2017 at 6:37 AM, Chris Olivier wrote: +1 for 1) — Jenkins On Thu, Nov 9, 2017 at 9:14 PM Naveen Swamy wrote: +1 on 1) On Nov 9, 2017,

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

+1 for 1 (non-binding) On Fri, Nov 10, 2017 at 6:37 AM, Chris Olivier wrote: > +1 for 1) — Jenkins > > > On Thu, Nov 9, 2017 at 9:14 PM Naveen Swamy wrote: > > > +1 on 1) > > > > > On Nov 9, 2017, at 8:59 PM, Steffen Rochel >

Re: [DISCUSSION] Adding labels to PRs

I have a weak preference for option #2, as this option really helps make releases easy, and encourages a well thought-through commit process. However a combo of #1 and #3 would also work well, and is less overhead. Note: probably obvious, but whichever mechanism we choose, let's remember to