From owner-freebsd-ports@FreeBSD.ORG Wed Oct 13 18:49:22 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF99216A4CE for ; Wed, 13 Oct 2004 18:49:22 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBB9F43D46 for ; Wed, 13 Oct 2004 18:49:22 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id i9DInGLU020736; Wed, 13 Oct 2004 11:49:16 -0700 (PDT) Received: from [10.1.1.245] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0)i9DInCJo019736; Wed, 13 Oct 2004 11:49:13 -0700 (PDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <9171258B-1D48-11D9-8DBB-003065ABFD92@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Wed, 13 Oct 2004 14:49:09 -0400 To: FreeBSD ports X-Mailer: Apple Mail (2.619) cc: Oliver Eikemeier cc: Kris Kennaway Subject: Re: Email nagging, was: Re: Ports with version numbers going backwards: graphics/gd,japanese/gd, ukrain... X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Oct 2004 18:49:23 -0000 On Oct 12, 2004, at 7:30 PM, Oliver Eikemeier wrote: > Uhm, I wonder why you are fine with hourly `INDEX build failed' > messages, but oppose those addressing PORTVERSION. Any crucial > difference I'm missing? Yes. :-) Please note that I did not say I was fine with hourly "INDEX build failed" messages. Those are tolerable, but I wish those were generated less often as well. Automated email nagging should be tuned so that it provides alerts when something breaks, and periodic reminders if something is left unfixed. However, too much nagging is counterproductive because people ignore them or file the notices into junk mail. This is particularly true for the case where the people receiving the mail cannot fix the problem which they are being nagged about. ----- On Oct 12, 2004, at 8:49 PM, Kris Kennaway wrote: > You're not distinguishing that it's important for the committers to be > told about the version decrement (so they can fix it), but users don't > need to know about it. OTOH, reporting INDEX failures to users is > important because otherwise someone has to answer all of the support > emails that arise when users notice on their own (because their index > build fails). Yes, I've heard you say this before, and I accept that messaging all users (not just committers) for failed INDEX builds serves a useful purpose. Beyond that, my memory suggests that at least sometimes, a non-committer-- often the maintainer of an affected port-- will figure out what's wrong with an INDEX build and suggest a fix in a timely enough fashion that doing so is helpful to the committers. -- -Chuck