Re: MXNet Name Change?

I agree with comments on not breaking momentum by rebranding the name. It's also my first time hearing about the pronunciation being "mixnet" and not "m-x-net" so that clarification, along with the motivation behind the name, feature parity, would strengthen the brand more. To that point, Sean

Turned off PR builds

I turned off PR builds to prioritize testing our v0.11.0 branch for cutting RC1. The following PR builds that were in progress, and any new PR's or updated PR's, will be affected and will pick back up once we cut the release and re-enable PR builds tonight: 7433 7442 7458

Re: how CI system works in MxNet?

As mentioned by Sheng this is an ongoing issue and a JIRA ticket has been filed to Apache Infra team, will follow up tomorrow if status hasn't been updated. https://issues.apache.org/jira/browse/INFRA-14840 On Sun, Aug 13, 2017 at 9:21 AM, Nan Zhu wrote: > no, I mean the

[VOTE] Release MXNet version 0.11.0

This is the vote to release Apache MXNet (incubating) version 0.11.0. Voting will start now (Saturday, August 12, 2017 9:26 AM UTC) and close Tuesday, August 15, 2017 9:26 AM UTC. Link to release notes: https://cwiki.apache.org/confluence/display/MXNET/v0.11.0+Release+Notes Link to release

Re: MXNet project web page

s://www.apache.org/foundation/marks/pmcs#introduction > > Cheers, > Chris > > > On 8/4/17, 11:20 AM, "Ly Nguyen" <nguyen...@gmail.com> wrote: > > Hi Isabelle, > > As Mu mentioned we are in the process of transferring our website to > ht

Halting code merges until CI is stable

Hi, a pending item for our release is adding license headers to all source files. We first need to stabilize the CI before we can merge the license headers, which is a very big change. To avoid introducing any breaking changes, we need to halt merges of new features. Until we have stability and

Release plan - MXNET 0.11.0

We are starting the process to prepare for MXNET v0.11.0 release. We have drafted release notes https://cwiki.apache.org/confluence/display/MXNET/v0.11.0+Release+Notes to cover the tasks under this release. A release candidate will be cut on Monday, August 7th, and voting will commence from then

Release Process

A more detailed release process for release managers as the target audience has been documented here: https://cwiki.apache.org/confluence/display/MXNET/Release+Process There are some details such as example commands that are still TODOs and will be added as we go through the first official

Re: Stop automated message from Apache Git Service

JIRA ticket: https://issues.apache.org/jira/browse/INFRA-14732 On Fri, Jul 28, 2017 at 2:10 PM, Naveen Swamy wrote: > Can we move such emails to comm...@mxnet.incubator.apache.org or similar ? > > Whoever interested can subscribe on that. > > Thanks, Naveen > > On Fri, Jul

Re: Granting access to Jenkins

Best, > Sebastian > > > On 27.06.2017 23:02, Ly Nguyen wrote: > >> Now that I'm a committer and have an account (thanks all!) I still need >> the >> following to move migration forward: >> >> 1) Grant me access to Jenkins: >> https://cwiki.apache.org/conflu

IMPORTANT: Link accounts to Apache today 7/12

As mentioned in the migration FAQ, if you currently have any kind of write access to MXNet repo, once migration happens, YOU WILL LOSE IT unless you do the following. If you haven't already, please link your Apache accounts (you need to already be a committer) to Gitbox here:

Re: Rcpp licensing in Apache MXNet

have the answer. > > Best, > > KK > > On Tue, Jul 11, 2017 at 10:50 AM, Ly Nguyen <nguyen...@gmail.com> wrote: > > > Hi @KK, any updates from legal on whether excluding the R pkg is a > solution > > for our next release? > > > > On Mon, Jul 10, 2017

Re: Rcpp licensing in Apache MXNet

Hi @KK, any updates from legal on whether excluding the R pkg is a solution for our next release? On Mon, Jul 10, 2017 at 10:49 AM, Qiang Kou wrote: > Thank you for the info. > > As I understand, if we skip the R pkg when releasing the a new version of > MXNet, everything is

Re: MXNet -> Apache Migration proposal

s/ On Mon, Jul 10, 2017 at 12:36 PM, Ly Nguyen <nguyen...@gmail.com> wrote: > From Mu: > Please preserve the following hooks after transferring: > -http://mxnet.io:8080/github-webhook/ (docs deployment) > -https://ci.appveyor.com/api/github/webhook > all other hooks can be r

Re: Typo in the documentation

I've posted an issue here: https://github.com/dmlc/mxnet/issues/6721 As soon as I get access to the original graphic I can make the change. On Thu, Jun 15, 2017 at 9:09 AM, Ly Nguyen <nguyen...@gmail.com> wrote: > Hi Sebastian. Thank you for spotting this. We will b

Granting access to Jenkins

Hi, I'm helping with the code migration of MXNet to Apache and need to set up jobs on Jenkins. It seems I would need to be a committer (detailed below) which I'm currently not. What would the group suggest for me in this case?