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 B4840D879 for ; Thu, 20 Dec 2012 17:12:32 +0000 (UTC) Received: (qmail 92290 invoked by uid 500); 20 Dec 2012 17:12:32 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 92237 invoked by uid 500); 20 Dec 2012 17:12:32 -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 92228 invoked by uid 99); 20 Dec 2012 17:12:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Dec 2012 17:12:31 +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 (athena.apache.org: domain of dsw@cloudera.com designates 209.85.212.41 as permitted sender) Received: from [209.85.212.41] (HELO mail-vb0-f41.google.com) (209.85.212.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Dec 2012 17:12:27 +0000 Received: by mail-vb0-f41.google.com with SMTP id l22so3998884vbn.14 for ; Thu, 20 Dec 2012 09:12:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=ePQds3r8wKvUXUNI+uPDsQc+CVISjnT/elI1VTQ0/FQ=; b=Z42R/elABL2Xk7b+8KLybbN1OfwVP0tA8651Fc0nW1wgPUrnxSFGBQuT2RTnmil0On gAT6Jk2cACR+fAzgRE7RjBamyUYMRisx6kgobnBse3CfOVaT4RwOTgIDwsCz5ZmVh+5M vxU4CVhgEJIV//IsoKyidCEZj/8Clc69BScTqdVIlIDmKP3Ub+KADxVPpZi0a9d+BrsC iRBvjyneUqIzkHg5ENj3q0brjBIbHwZEoLyUJbdBGOssUt/G4g69FvSsWhjmAmhDJpXk fPeAF6MB16a3qF0gF5/Hbx1yuw6ssoW7hwlfA4IuxZBfTNGvjonbrr1+6hHOpaaoAZGj rohg== MIME-Version: 1.0 Received: by 10.52.17.244 with SMTP id r20mr13620662vdd.29.1356023526271; Thu, 20 Dec 2012 09:12:06 -0800 (PST) Received: by 10.58.241.144 with HTTP; Thu, 20 Dec 2012 09:12:06 -0800 (PST) In-Reply-To: References: Date: Thu, 20 Dec 2012 09:12:06 -0800 Message-ID: Subject: Re: NOTICE: Dev list will start getting notification of newly opened issues WAS -> Re: Notifications of newly-created JIRAs on dev@ From: Dave Wang To: dev@hbase.apache.org Content-Type: multipart/alternative; boundary=bcaec502d4c8972c4904d14bd47e X-Gm-Message-State: ALoCoQnHyKOJQHfgKQuxz5J7VQ2iWjdQgll+ZaqQMDkQds2fQX9olwZvp9HwY1TL2qOvOCT9RaMK X-Virus-Checked: Checked by ClamAV on apache.org --bcaec502d4c8972c4904d14bd47e Content-Type: text/plain; charset=ISO-8859-1 Without any exaggeration, I am positively giddy with anticipation. Thanks Stack! - Dave On Thu, Dec 20, 2012 at 9:05 AM, Stack wrote: > Following up on the below conversation thread, I will make the adjustment > up in JIRA later today so newly opened JIRAs will show in the dev list (To > be more exact, CREATED, RESOLVED, CLOSED, and REOPENED). The general > notion is that issues@hbase.apache.org is too hard to follow because it > has > ALL issue changes -- both mundane (the majority) and the sublime -- and > there is just too much volume to follow if one is trying to keep up. If > dev gets a mail when an issue is opened, folks can select those issues they > are interested in and 'watch' them in JIRA and ignore all the rest. > > If objection, please raise it now on this thread else, later today expect > JIRA mail here in dev. > > Thanks, > St.Ack > > > On Wed, Dec 5, 2012 at 10:14 AM, Sergey Shelukhin >wrote: > > > +1... too many updates on the issues@ list. > > > > On Tue, Dec 4, 2012 at 10:36 PM, Andrew Purtell > > wrote: > > > > > If you can't keep up, nobody can! > > > > > > > > > On Wed, Dec 5, 2012 at 2:25 PM, Stack wrote: > > > > > > > On Tue, Dec 4, 2012 at 6:50 PM, Ted Yu wrote: > > > > > > > > > I relied heavily on the notifications from issues@ so that I can > > keep > > > > > myself up-to-date on latest development. > > > > > > > > > > > > > > Can you not do some creative gmail filter foo so all issue edits show > > up > > > > under a single new issues filter -- those from issues@ and the mail > to > > > dev > > > > about created, reopened, and resolved issues? > > > > > > > > > > > > > Maybe we can create a new mailing list which satisfies Dave's > > > > description. > > > > > > > > > > > > > My sense is that Dave is speaking for a majority of hbase devs; a > group > > > who > > > > want to follow along but at a coarser granularity. The number of us > > able > > > > to take the full issues mailing list firehose is shrinking radically. > > > For > > > > example, I can no longer keep up. > > > > > > > > St.Ack > > > > > > > > > > > > > > > > -- > > > Best regards, > > > > > > - Andy > > > > > > Problems worthy of attack prove their worth by hitting back. - Piet > Hein > > > (via Tom White) > > > > > > --bcaec502d4c8972c4904d14bd47e--