Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0626C9EC7 for ; Thu, 16 May 2013 03:14:59 +0000 (UTC) Received: (qmail 21419 invoked by uid 500); 16 May 2013 03:14:58 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 21329 invoked by uid 500); 16 May 2013 03:14:58 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 21300 invoked by uid 99); 16 May 2013 03:14:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 May 2013 03:14:57 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.215.51 as permitted sender) Received: from [209.85.215.51] (HELO mail-la0-f51.google.com) (209.85.215.51) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 May 2013 03:14:51 +0000 Received: by mail-la0-f51.google.com with SMTP id lx15so565203lab.38 for ; Wed, 15 May 2013 20:14:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=qXvKMlc2+4+5GPHbYOh1Tb81+GmEn6Ns9o7YtZJV8yU=; b=uU5VcIk8kmxug7HDTPAEBLPCLjudoC436x8eL4cMOcbG4Pcibzcj5aE69lxGNszqbf TyYYt0JNSnZw8Yvyd5bnmP87yszd6LlojybR4dsWYdTQvd+1OOADe1PIAT7WhQ0Wyjm/ nE9UfB2zTHkNjg00gPIT2opsTQqkZomX6sXmXnjQ9ZV9n4LRyC5xzKVkWB6knU3NLAKr KXV15cPmMYqNijRYCIZrtZMOOL2mldevUDLHDDq5Dnfo/Ay17eP8oLeXB1+FSLb/ahpB 6YLSma9vncTvPd0rIS+oRzeh7rDR4tDV/aOO60N5ZpcI93P7RH0/Ids5agIuszpvVC7n tRxA== MIME-Version: 1.0 X-Received: by 10.112.201.4 with SMTP id jw4mr19130217lbc.47.1368674071203; Wed, 15 May 2013 20:14:31 -0700 (PDT) Received: by 10.112.136.104 with HTTP; Wed, 15 May 2013 20:14:31 -0700 (PDT) In-Reply-To: References: <1368661402.38868.YahooMailNeo@web140606.mail.bf1.yahoo.com> Date: Wed, 15 May 2013 20:14:31 -0700 Message-ID: Subject: Re: 0.94 Security + Jira From: Ted Yu To: dev@hbase.apache.org Content-Type: multipart/alternative; boundary=001a11c37170d3d4de04dccd43e0 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c37170d3d4de04dccd43e0 Content-Type: text/plain; charset=ISO-8859-1 How about making HBase-0.94-security build as frequently as HBase-0.94 build ? This way, we can see test failure(s) that would only occur in secure build. Cheers On Wed, May 15, 2013 at 7:55 PM, Jonathan Hsieh wrote: > The problem is that it runs infrequently and drops little jira updates that > polutes our inboxes about things we've fixed last week. If not off then it > should be more frequent so that it only shows things from yesterday. > > Jon. > > > On Wed, May 15, 2013 at 4:43 PM, lars hofhansl wrote: > > > Or we can run it more frequently...? > > > > > > > > ----- Original Message ----- > > From: Elliott Clark > > To: "dev@hbase.apache.org" > > Cc: > > Sent: Wednesday, May 15, 2013 3:43 PM > > Subject: 0.94 Security + Jira > > > > Should we turn off jira commenting for the 0.94 security job? It just > > comes back around so late that the only thing it does for me is make > > it hard to determine what jira have comments that I need to read. > > > > > > > -- > // Jonathan Hsieh (shay) > // Software Engineer, Cloudera > // jon@cloudera.com > --001a11c37170d3d4de04dccd43e0--