Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6EC551742E for ; Thu, 21 May 2015 10:00:56 +0000 (UTC) Received: (qmail 72623 invoked by uid 500); 21 May 2015 10:00:56 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 72583 invoked by uid 500); 21 May 2015 10:00:56 -0000 Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.incubator.apache.org Delivered-To: mailing list dev@ignite.incubator.apache.org Received: (qmail 72572 invoked by uid 99); 21 May 2015 10:00:56 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 May 2015 10:00:56 +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 CD889C11B9 for ; Thu, 21 May 2015 10:00:55 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.97 X-Spam-Level: *** X-Spam-Status: No, score=3.97 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id i6MCba7xNTqc for ; Thu, 21 May 2015 10:00:55 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with SMTP id 96E30453D8 for ; Thu, 21 May 2015 10:00:54 +0000 (UTC) Received: (qmail 72539 invoked by uid 99); 21 May 2015 10:00:54 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 May 2015 10:00:54 +0000 Received: from mail-oi0-f44.google.com (mail-oi0-f44.google.com [209.85.218.44]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id C73811A02FC for ; Thu, 21 May 2015 10:00:53 +0000 (UTC) Received: by oiko83 with SMTP id o83so56756433oik.1 for ; Thu, 21 May 2015 03:00:52 -0700 (PDT) X-Gm-Message-State: ALoCoQkyvzr4derj+ncq5pZoBWnUJqo2dvODfa/coR4Khtv1hzW1T+9tcEa1CEbIQOzgHmcw7Y9R X-Received: by 10.60.39.65 with SMTP id n1mr1586090oek.31.1432202452713; Thu, 21 May 2015 03:00:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.190.70 with HTTP; Thu, 21 May 2015 03:00:12 -0700 (PDT) In-Reply-To: <555DA9EE.6050901@apache.org> References: <20150401032304.GF1657@boudnik.org> <20150428173039.GC28615@boudnik.org> <20150505203112.GZ28615@boudnik.org> <20150519175300.GQ28615@boudnik.org> <20150520215701.GA20638@tpx> <555DA9EE.6050901@apache.org> From: Dmitriy Setrakyan Date: Thu, 21 May 2015 03:00:12 -0700 Message-ID: Subject: Re: Fwd: automatic patch validation on TC To: "dev@ignite.incubator.apache.org" Content-Type: multipart/alternative; boundary=089e013d085a70da990516949e1d --089e013d085a70da990516949e1d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, May 21, 2015 at 2:48 AM, Branko =C4=8Cibej wrote= : > On 21.05.2015 11:35, Dmitriy Setrakyan wrote: > > Are we saying that non-contributors can attach patches? > > > Slow down. Anyone who sends a patch is, by definition, a contributor. > Whether or not you decide to use the patch is a different matter. You > don't want to invent any extremely paranoid access control; that's > contrary to the whole point of open source. > Brane, as far as I know, in order for someone to start working on a ticket we need to add him/her to the list of "contributors" in Jira. Otherwise the ticket cannot even be assigned to that person. I thought that only the people on the Jira "contributor" list can attach patches. Is this not so? If not, can we configure Jira to work in that way? > > If you don't want to automatically test patches in your test > environment, then by all means don't do that. You can invent a 'patch > reviewed' state in Jira that needs explicit permission to be set, and > only send the patch to CI once a committer has reviewed the patch. > > -- Brane > > --089e013d085a70da990516949e1d--