From owner-freebsd-security Thu Dec 2 14: 7:37 1999 Delivered-To: freebsd-security@freebsd.org Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (Postfix) with ESMTP id 5BAB514F37; Thu, 2 Dec 1999 14:07:31 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.3/8.9.3) with ESMTP id RAA90130; Thu, 2 Dec 1999 17:06:03 -0500 (EST) (envelope-from matt@zigg.com) Date: Thu, 2 Dec 1999 17:06:03 -0500 (EST) From: Matt Behrens To: "Jung, Michael" Cc: "'Wes Peters'" , "'Steve Reid'" , "'Sheldon Hearn'" , "'Bill Swingle'" , "'security@FreeBSD.ORG'" , "'Jordan Hubbard'" Subject: RE: [btellier@USA.NET: Several FreeBSD-3.3 vulnerabilities] In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Today, Jung, Michael wrote: : Why not just have the PR system email the ORIGINATOR when : the PR is closed? : : This way the originator is informed of the update and it's give them : the opportunity to make sure the problem is really resolved. : : At our organization the ORIGINATOR actually receives email : any time the status changes on a ticket. Call me crazy, but I think this happens. (Geeze, I've submitted so many but my memory is failing me...) :-) I like Wes's idea, with one caveat: there are quite a few PRs that are silly -- ones that are really pleas for support. There should ideally be some kind of fallback closing method for those. I know Bugzilla has the ``WORKSFORME'' state which might be useful. Matt Behrens Owner/Administrator, zigg.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message