Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-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 EDE5FDFC6 for ; Fri, 14 Sep 2012 07:13:49 +0000 (UTC) Received: (qmail 49420 invoked by uid 500); 14 Sep 2012 07:13:49 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 49177 invoked by uid 500); 14 Sep 2012 07:13:49 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 49136 invoked by uid 99); 14 Sep 2012 07:13:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Sep 2012 07:13:47 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of hekonsek@gmail.com designates 209.85.223.173 as permitted sender) Received: from [209.85.223.173] (HELO mail-ie0-f173.google.com) (209.85.223.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Sep 2012 07:13:41 +0000 Received: by iebc10 with SMTP id c10so7763236ieb.32 for ; Fri, 14 Sep 2012 00:13:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GX7n4Ig6/JbW05rilJRlq7sli/zc1SNEbBn2ckl9f6w=; b=R0tuNAv5eTpo/UVHmVflNs6vt0qUTJVfRqdOMs4n4pRv9Dbs1s84qQzlcWIQAIPpdY ddT/6G5MrCIr4xTcebdslKyYo2A0YmaiOA8RiSxVfF5zDo8g16SCb3TUT97zQbCnqoJZ ajTwO9R1rsOuVoyeZutelAI2WBZwB9qpJZUiROOqnHvM4+HtOB1t0Jmx+psXeR9UoAL/ Sb0feiaxbjzR3DDPPgOX2nuPFmBva4NyB4TerTfPaKMhLFlQoAmKs/BKBM6Uq2JEQImN f2QycBvz+YYb0kBlAUptrUTG5dV9y5thppqOwjPIlEp0H+h3E2Oiz7H+zhbipFi1Duzg l0FA== MIME-Version: 1.0 Received: by 10.50.161.234 with SMTP id xv10mr1834397igb.68.1347606800503; Fri, 14 Sep 2012 00:13:20 -0700 (PDT) Received: by 10.64.36.9 with HTTP; Fri, 14 Sep 2012 00:13:20 -0700 (PDT) In-Reply-To: References: <20120712195130.GA21221@tarsus.local2> <20120715145321.GB23706@tarsus.local2> Date: Fri, 14 Sep 2012 09:13:20 +0200 Message-ID: Subject: Re: Accept mails on committs@camel.apache.org from camel-extra.apache-extras.org@codespot.com From: Henryk Konsek To: =?ISO-8859-1?Q?Christian_M=FCller?= Cc: dev@camel.apache.org Content-Type: text/plain; charset=ISO-8859-1 > We do not receive many issues via Google. If the notification mechanism > works, we will get a mail at issues@ and could create an JIRA issue at > Apache, link them together and update the Apache JIRA issue until it is > resolved. Than we can close both issues. Actually I see no point in maintaining both Jira and Google Issues. Google Issues do not provide any value added IMHO. And somebody will have to link issue to Jira after notification has been sent. The another thing I don't like in Google Issues at Camel Extra is that they create the illusion that Camel Extra issues are handled separately from the regular Camel (what is not true, since we create camel-extra issues in Jira as well). In case you decided to close the Google Issues on behalf of Jira - just let me know. I'll migrate the existing issues and hide the issues tab. -- Henryk Konsek http://henryk-konsek.blogspot.com