From dev-return-5702-archive-asf-public=cust-asf.ponee.io@mxnet.incubator.apache.org Sat Mar 23 00:41:23 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 7E1EC18064D for ; Sat, 23 Mar 2019 01:41:22 +0100 (CET) Received: (qmail 27659 invoked by uid 500); 23 Mar 2019 00:41:21 -0000 Mailing-List: contact dev-help@mxnet.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mxnet.incubator.apache.org Delivered-To: mailing list dev@mxnet.incubator.apache.org Received: (qmail 27647 invoked by uid 99); 23 Mar 2019 00:41:20 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Mar 2019 00:41:20 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 65E26C559B for ; Sat, 23 Mar 2019 00:41:20 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.399 X-Spam-Level: X-Spam-Status: No, score=-0.399 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=cs.washington.edu Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id DX7NQkiwhZkS for ; Sat, 23 Mar 2019 00:41:19 +0000 (UTC) Received: from mx6.cs.washington.edu (mx6.cs.washington.edu [128.208.47.51]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 2CAA5610F9 for ; Sat, 23 Mar 2019 00:41:18 +0000 (UTC) Received: from mx6.cs.washington.edu (localhost [IPv6:0:0:0:0:0:0:0:1]) by mx6.cs.washington.edu (8.15.2/8.15.2/1.23) with ESMTP id x2N0fGQ4113563 for ; Fri, 22 Mar 2019 17:41:16 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.washington.edu; s=csw201206; t=1553301676; bh=ZwX/MYVwgE39P3KgfYEzxABZxenIJ2SS10PiZoSxQgs=; h=References:In-Reply-To:From:Date:Subject:To; b=K9DdsSyuycVX0kpc0OqXgwvKCsZ1avBXJzi3W3Tr9CFZC43A/CGx/bx9i7svLb7ju hJhyu2+etBePA04OgXqmyUh3kgKRViJM/+iyqGb0ICmOOsvSrMe6Haemd7MZbpAlyA VJOCAW6Yqp29QO78e2s+K11IBry35WmcFWRqDXKQ= Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) (authenticated bits=0) by mx6.cs.washington.edu (8.15.2/8.15.2/1.23) with ESMTPSA id x2N0fEKi113560 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 22 Mar 2019 17:41:16 -0700 Received: by mail-wr1-f42.google.com with SMTP id y7so16478wrn.11 for ; Fri, 22 Mar 2019 17:41:15 -0700 (PDT) X-Gm-Message-State: APjAAAWS9+QCZ28W2aC1Fysm1Tzzoe6alx15Ne6cZyvo+gtdo+5+kRzu HCaKuscV3ANJ/hFZK/8gncBKlKmhJXdSBaJzlHA= X-Google-Smtp-Source: APXvYqxK3IMFT47cBIMxyS1XuzL62/J/adwiDuMeQKRc7Ni7HW4vzAbbeHJNOvDCMzaaxvVTnNJdMFIR/NetI5zAvf4= X-Received: by 2002:adf:edca:: with SMTP id v10mr7806802wro.157.1553301674453; Fri, 22 Mar 2019 17:41:14 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Tianqi Chen Date: Fri, 22 Mar 2019 17:41:03 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [DISCUSS] Rebrand Gluon to MXNet imperative or something MXNet. To: dev@mxnet.incubator.apache.org Content-Type: multipart/alternative; boundary="00000000000088f06f0584b83a91" --00000000000088f06f0584b83a91 Content-Type: text/plain; charset="UTF-8" Change the name gluon will result in a significant problem of backward compatibility for many of the current users, and that would be a huge -1 for the current community. One possibility is to do that is to have a clear roadmap of 2.0(which gives the message of non-backward compatible) and we can discuss which features consolidate, but perhaps that will require a bit more thoughts and coordinated effort. Tianqi On Fri, Mar 22, 2019 at 5:39 PM Junru Shao wrote: > @Tianqi For sure GluonCV and GluonNLP should go with the current name. No > reason to change. > > @Lin If customers are interested, I guess we could say they are awesome > toolkits built on top of MXNet Gluon API, and perfect illustration to write > clever and powerful code on the top of it. > --00000000000088f06f0584b83a91--