Return-Path: Delivered-To: apmail-maven-continuum-dev-archive@www.apache.org Received: (qmail 58545 invoked from network); 1 Aug 2007 02:11:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Aug 2007 02:11:02 -0000 Received: (qmail 30938 invoked by uid 500); 1 Aug 2007 02:11:02 -0000 Delivered-To: apmail-maven-continuum-dev-archive@maven.apache.org Received: (qmail 30907 invoked by uid 500); 1 Aug 2007 02:11:02 -0000 Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-dev@maven.apache.org Delivered-To: mailing list continuum-dev@maven.apache.org Received: (qmail 30896 invoked by uid 99); 1 Aug 2007 02:11:02 -0000 Received: from Unknown (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jul 2007 19:11:02 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [210.50.30.235] (HELO mx05.syd.iprimus.net.au) (210.50.30.235) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2007 02:10:58 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAM6Ir0Y6skK9/2dsb2JhbAAN X-IronPort-AV: E=Sophos;i="4.19,206,1183298400"; d="scan'208";a="58636454" Received: from 189.034.dsl.brs.iprimus.net.au (HELO [192.168.237.213]) ([58.178.66.189]) by smtp05.syd.iprimus.net.au with ESMTP; 01 Aug 2007 12:10:34 +1000 Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: References: <4F93F9D0-BE70-43A7-83FE-24D96322ACF3@apache.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1888241C-2921-437A-8C65-40567E8B992A@apache.org> Content-Transfer-Encoding: 7bit From: Brett Porter Subject: Re: Solving the notification problem Date: Wed, 1 Aug 2007 12:10:31 +1000 To: continuum-dev@maven.apache.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org On 01/08/2007, at 12:01 PM, Jesse McConnell wrote: > well, 1.1 is in beta now so ideally no more features, but maybe we > just call > this a bug fix for now.. yeah, I'm looking more for a small improvement than a revolution. Avoiding schema changes and such. I really should have said something before beta-1. > > I guess the first suggestion might be a batch email option with a > summary > presented at the top of the mail...that would almost have to be on > a per > notifier though, but that is made easier by the group level inherited > notifiers...That is another db schema change though :) Yeah, and we don't really have anything that can keep track of when to send that - there's no notion of a group schedule. > > We could alter the notifications to prepare web reports that have > the links > mailed out, and suppress mails based on time or if a given link has > been > mailed recently. We already have the web reports, so maybe a configurable time threshold is the best (ok, it might require an addition to the notifier schema, but it's innocuous.... :) > > what conditions do we find the highest lvl of easily ignorable > mails go out? > > I can think of things like SCM outage and things like that...out of > memory > errors... Errors are definitely the biggest nuisance, and probably chain reaction failures. If we could even take care of the error condition stuff it might be enough. - Brett