Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E1152200B49 for ; Wed, 20 Jul 2016 07:31:55 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DFB53160A8B; Wed, 20 Jul 2016 05:31:55 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 31DB9160A76 for ; Wed, 20 Jul 2016 07:31:55 +0200 (CEST) Received: (qmail 81370 invoked by uid 500); 20 Jul 2016 05:31:54 -0000 Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hawq.incubator.apache.org Delivered-To: mailing list dev@hawq.incubator.apache.org Received: (qmail 81356 invoked by uid 99); 20 Jul 2016 05:31:54 -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; Wed, 20 Jul 2016 05:31:54 +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 B05E0187990 for ; Wed, 20 Jul 2016 05:31:53 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -3.446 X-Spam-Level: X-Spam-Status: No, score=-3.446 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id OoeE8papEBX3 for ; Wed, 20 Jul 2016 05:31:52 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with SMTP id 602205F4E7 for ; Wed, 20 Jul 2016 05:31:52 +0000 (UTC) Received: (qmail 81349 invoked by uid 99); 20 Jul 2016 05:31:51 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jul 2016 05:31:51 +0000 Received: from mail-it0-f49.google.com (mail-it0-f49.google.com [209.85.214.49]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 264B91A0042 for ; Wed, 20 Jul 2016 05:31:51 +0000 (UTC) Received: by mail-it0-f49.google.com with SMTP id u186so108618103ita.0 for ; Tue, 19 Jul 2016 22:31:51 -0700 (PDT) X-Gm-Message-State: ALyK8tJSlJ9X48AgAWLb61GAZVuEAiVKz9U8Clq93r7hgkVej2pNwpWMcH7Gr08As3y7D6hvT8u3UHAd26dzJA== X-Received: by 10.36.66.19 with SMTP id i19mr7870164itb.30.1468992710490; Tue, 19 Jul 2016 22:31:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.16.233 with HTTP; Tue, 19 Jul 2016 22:31:49 -0700 (PDT) In-Reply-To: References: From: Lili Ma Date: Wed, 20 Jul 2016 13:31:49 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Jira comments vs PR comments To: dev@hawq.incubator.apache.org Content-Type: multipart/alternative; boundary=001a11405b82afc5f305380a848c archived-at: Wed, 20 Jul 2016 05:31:56 -0000 --001a11405b82afc5f305380a848c Content-Type: text/plain; charset=UTF-8 Agree! Just keeping the "issue links to" is enough to track the pull request. Leaving the comments on JIRA there is more neat. Thanks Lili 2016-07-20 10:34 GMT+08:00 Paul Guo : > +1. Github has already have fine-grained notification mechanism. I think > JIRA > could just pull the initial git pull request info, not each comment in > github. > > I guess this is either a JIRA configuration issue or an asf/infrustructure > issue. > > 2016-07-20 2:57 GMT+08:00 Goden Yao : > > > 2nd that. JIRA right now can already link to the PR under "issue links > to" > > section. (e.g.: https://issues.apache.org/jira/browse/HAWQ-936 ) > > Not sure if that was automatic or manual but I prefer that way instead of > > auto-pulling every PR comment into the JIRA (even closing PR is a > comment). > > > > JIRA discussion should be focused on the problem to solve and design, > etc. > > While PR comments are mainly for coding details, logic errors, naming > > issues, formats, coding style etc. > > > > -Goden > > > > On Tue, Jul 19, 2016 at 11:52 AM Shivram Mani > > wrote: > > > > > Its great that Jira and github has been linked, but this integration is > > > also making it hard for us to skim through actual comments posted in > > Jira. > > > Jiras usually end up being innundated with every single comment posted > in > > > the pull request. > > > This makes it hard for us to actually read through/search for actual > > > comments/discussions posted on the Jira amidst the pull requestion > > > notifications for each comment. > > > > > > Can we disable pull request comment based notifications from being > posted > > > on the Jira ? > > > Thoughts ? > > > > > > -- > > > shivram mani > > > > > > --001a11405b82afc5f305380a848c--