From dev-return-5194-archive-asf-public=cust-asf.ponee.io@mxnet.incubator.apache.org Thu Dec 20 22:00:49 2018 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 9F1B6180648 for ; Thu, 20 Dec 2018 22:00:48 +0100 (CET) Received: (qmail 75673 invoked by uid 500); 20 Dec 2018 21:00:47 -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 75660 invoked by uid 99); 20 Dec 2018 21:00:47 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Dec 2018 21:00:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 84808183B9B for ; Thu, 20 Dec 2018 21:00:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.799 X-Spam-Level: * X-Spam-Status: No, score=1.799 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id FtpLjqjpcn2M for ; Thu, 20 Dec 2018 21:00:45 +0000 (UTC) Received: from mail-oi1-f178.google.com (mail-oi1-f178.google.com [209.85.167.178]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 741485FB9E for ; Thu, 20 Dec 2018 21:00:44 +0000 (UTC) Received: by mail-oi1-f178.google.com with SMTP id u18so3042465oie.10 for ; Thu, 20 Dec 2018 13:00:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=otUEjEIV8QYaSDSeNSrdqhCFbM1J9ydQM+dSW6bOrno=; b=YMNNq08BsWVrT9je7iVuKLTQE6ewca9VXeIGUu9e4gWQpGoMRbZ/kYtivH9Q0UeaQj Wf6WgzklRwSXo8FYHQd2Mv3LikN8ZP3l+6ifjp6UO9er4/SmrHKjS++Un3PoYWZqIpnP V9vAcAWLepYJQcHU8Ets88h2J1gF/AIaDtrq8++I8EZzfOCmCE7ROlRiqj48pt8kQQ4M yG/DPBLKTv435FrPbCRNa2tddj7ztYBBrrWjJ1hMME3prGZbPiVyfIR+0T49Q1Lv29ep ka4i72BmCUlpaeORmV9AKgVq4Opthrk2DqYQmhZ/xqhUizPObrsPKeWMYDhzdA38quSC Yw9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=otUEjEIV8QYaSDSeNSrdqhCFbM1J9ydQM+dSW6bOrno=; b=EYNdo6/AnUWr7E0jmJOjQqzRxAny2pPCrSr3w6pf0mvUsS7t7hQmCtsgrXW1jeEO5O mZwHhHUUnnjkqKJdBy9yTDIGGLNqd7v7LNK8PGK+HoQQ+eu/pZwaIcDaYcJah1IGbiu6 98ri4V3EOlcpapZyXNjT4AHBudJrNY270c4qPGXu6jujaxnYIVjRGiuh37mOz6arU/xe Vqv5d4JBCl9sXQFfNosfRA+YN9TObVl7J/9/C7C9vDssFNH1I9QFTD9GKmAYvENCWUwQ LYLg2Jb9KQ6EHKTeJF0+m+qKL4h0UIYmTDHN65tT36c63P0AFw0MruAa/0U4BFGXBHCi bvzQ== X-Gm-Message-State: AA+aEWZpvGg+Pxcx2W4JccLJ+XOSv8Ooq2kmGzNB19nQ9xC6GEwN2NLf vDHRpiAa3ezqyxF3fazXBCWtOBss3z+MGhBV233EWw== X-Google-Smtp-Source: AFSGD/Wmie5M+EtqA6f5sWkIzHUon14OjVyY4YjHX3ZvLyUy6qc3GmvP77osuo5nJ2dDc1V9c1LVxWsPamxbrDhaRt0= X-Received: by 2002:aca:c650:: with SMTP id w77mr201891oif.122.1545339642734; Thu, 20 Dec 2018 13:00:42 -0800 (PST) MIME-Version: 1.0 From: Lin Yuan Date: Thu, 20 Dec 2018 13:00:31 -0800 Message-ID: Subject: [Question] UI change policy in MXNet To: dev@mxnet.incubator.apache.org Content-Type: multipart/alternative; boundary="000000000000766e54057d7a6c84" --000000000000766e54057d7a6c84 Content-Type: text/plain; charset="UTF-8" Dear Community, As a contributor, I would like to know the current policy for updating UI of an operator. I understand UI change should be introduced in major release not minor release. However, it is still not quite clear to me regarding the UI change process: 1) Which guideline should we follow when updating the UI in MXNet operators? 2) Who should approve the UI change? 3) In case of backward compatibility, should we favor breaking the backward compatibility and update the release notes or adding a newer version of the operator like ***_v2? 4) Which operator should go to contrib and which be implemented as regular? Any clarification is appreciated and it is helpful to guide PR reviewers as well. Merry Christmas to ya'all! Lin --000000000000766e54057d7a6c84--