Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 71555 invoked from network); 20 Mar 2008 09:46:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Mar 2008 09:46:24 -0000 Received: (qmail 20917 invoked by uid 500); 20 Mar 2008 09:46:20 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 20863 invoked by uid 500); 20 Mar 2008 09:46:20 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 20852 invoked by uid 99); 20 Mar 2008 09:46:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Mar 2008 02:46:20 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of eljotpl@gmail.com designates 209.85.146.176 as permitted sender) Received: from [209.85.146.176] (HELO wa-out-1112.google.com) (209.85.146.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Mar 2008 09:45:40 +0000 Received: by wa-out-1112.google.com with SMTP id j4so1058217wah.1 for ; Thu, 20 Mar 2008 02:45:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; bh=FzcZW75IEEbGqG8WR1yE0xBE44T28PhJLTjH2sdEuXg=; b=AD2UUVy0Rr17uH6FwptOKdA7TA5oeNxh+4nE0I6B9oKlruqNZ91By9wSZAkCgsHzEjGpUgSiyZHRQRP7OUa+//6eAGITSk3VfmyG0ho5a97celzitKVNa60swWKjF72z2PMFB0V8d75+8stJRKL3JLg8t97I7ev2XCmYjFT40c4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:reply-to:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=Nh4a6FLMA1Zh4XJjb+iXgwaPT8Aqu12mNUYIaH+1kyZHq0VGFYwsvRy4v1BzCI0spZMPykyYFgdZjKquT6Z2ZcDQjbQEnuudLsQ67PeZP39S70h8kpdzDZDCvh/Drx7pEo+Rt2w0OtpkkaJLzCsNpv6I7lVOU9+bkKUqvv04Znw= Received: by 10.115.60.1 with SMTP id n1mr3168994wak.37.1206006350993; Thu, 20 Mar 2008 02:45:50 -0700 (PDT) Received: by 10.114.196.7 with HTTP; Thu, 20 Mar 2008 02:45:50 -0700 (PDT) Message-ID: <1b5bfeb50803200245w4ef58fd3x7b2df2411cb75db3@mail.gmail.com> Date: Thu, 20 Mar 2008 10:45:50 +0100 From: "Jacek Laskowski" Reply-To: jacek@laskowski.net.pl Sender: eljotpl@gmail.com To: dev@geronimo.apache.org Subject: Changing notification Scheme for Geronimo in JIRA to commits? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: 39cb09829b44a0be X-Virus-Checked: Checked by ClamAV on apache.org Hi, I wonder what's your opinion on changing the notification scheme in jira to send jira notifications to commits@g.a.o. I usually look at jira report and (try to) match it to appropriate svn changes that requires me switching between dev@ and commits@ back and forth. I know I could filter out jira notifications and place them in , but if most of us do this let's fix the issue rather than work it around. I think the email flood might frighten many potential developers (but it could be their best way to contribute to stay up-to-date too). Just thought I'd ask others for their views. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl