From dev-return-2220-archive-asf-public=cust-asf.ponee.io@mxnet.incubator.apache.org Fri Feb 23 18:07:24 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 75731180652 for ; Fri, 23 Feb 2018 18:07:23 +0100 (CET) Received: (qmail 81724 invoked by uid 500); 23 Feb 2018 17:07:22 -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 81710 invoked by uid 99); 23 Feb 2018 17:07:22 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Feb 2018 17:07:22 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id F14A6C045F for ; Fri, 23 Feb 2018 17:07:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -11.031 X-Spam-Level: X-Spam-Status: No, score=-11.031 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=2, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 3f7bkjgGmvYo for ; Fri, 23 Feb 2018 17:07:20 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id DB7085F216 for ; Fri, 23 Feb 2018 17:07:19 +0000 (UTC) Received: (qmail 81673 invoked by uid 99); 23 Feb 2018 17:07:19 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Feb 2018 17:07:19 +0000 Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id 2BEB71901 for ; Fri, 23 Feb 2018 17:07:17 +0000 (UTC) Received: by mail-wm0-f53.google.com with SMTP id z9so5811941wmb.3 for ; Fri, 23 Feb 2018 09:07:17 -0800 (PST) X-Gm-Message-State: APf1xPBlQ9/tvuetHtL9bQpVRH9J6xlKX/u3vzM3H8Cs8Z3XrTf1AALR R4sbLaE7p6zSVAhxu+WlpV2Sa2o/4tIOA4E+HRg= X-Google-Smtp-Source: AH8x2275qR7+ilBUF46dWOGocP6hRwynmBQ9GCmRqpBSMH23pXq0osJbiRi6uE2NLeueaWgn3h0rOoHjaGMiScEbpL0= X-Received: by 10.80.142.200 with SMTP id x8mr3718905edx.274.1519405636665; Fri, 23 Feb 2018 09:07:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.220.129 with HTTP; Fri, 23 Feb 2018 09:07:16 -0800 (PST) From: CodingCat Date: Fri, 23 Feb 2018 09:07:16 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: [VOTE] tracking code changes with JIRA by associating pull requests To: dev@mxnet.incubator.apache.org Content-Type: multipart/alternative; boundary="f403045c14fa3e460e0565e431ce" --f403045c14fa3e460e0565e431ce Content-Type: text/plain; charset="UTF-8" Hi, all To make the changes in code base more trackable, I would propose to link each PR with the a JIRA from now on: 1. most of PRs should be titled as [MXNET-???][MODULE_NAME] PR short description, where MXNET-??? is the JIRA ID, MODULE_NAME can be python, scala, symbol, etc. 2. only the very tiny fix, e.g. fix a typo, remove some unused variables, or the hotfix which brings the broken build back to track, can be filed without JIRA ID in title, In JIRA side, to link the issue with an arrived PR, we can run a script like https://github.com/apache/spark/blob/master/dev/github_jira_sync.py to update JIRA status (can be run in Jenkins) The benefits of applying such a flow include (but not limited to) 1. facilitate the release process: e.g., as long as tagging each JIRA with the correct affected version and fixed version, the release manager can quickly identify what are the changes applied in this version; or we can quickly identify whether there is any blocker issue in the JIRA 2. trackable changes any changes in MXNET can be quickly searched through JIRA or even through Google (JIRA looks like did something makes it more indexable by Google), If the vote gets pass, the plan in the near horizon includes 1. update JIRA with the modules names 2. write runbook for release manager/committer for releasing new version/merging patches, as well as contributors about the usage of JIRA 3. push the changes to the existing and coming PRs (this also needs the collaboration across the whole committer team) The vote will end at 12:00 p.m. of March 2nd, 2018 Best, Nan --f403045c14fa3e460e0565e431ce--