From owner-freebsd-ports-bugs@FreeBSD.ORG Mon Jul 17 20:20:22 2006 Return-Path: X-Original-To: freebsd-ports-bugs@hub.freebsd.org Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A953716A4E5 for ; Mon, 17 Jul 2006 20:20:22 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C45A43D4C for ; Mon, 17 Jul 2006 20:20:22 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k6HKKMKS022072 for ; Mon, 17 Jul 2006 20:20:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k6HKKMLq022067; Mon, 17 Jul 2006 20:20:22 GMT (envelope-from gnats) Date: Mon, 17 Jul 2006 20:20:22 GMT Message-Id: <200607172020.k6HKKMLq022067@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Erwin Lansing Cc: Subject: Re: ports/100446: relinquish maintainership X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Erwin Lansing List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jul 2006 20:20:22 -0000 The following reply was made to PR ports/100446; it has been noted by GNATS. From: Erwin Lansing To: Vivek Khera Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: ports/100446: relinquish maintainership Date: Mon, 17 Jul 2006 22:10:42 +0200 On Mon, Jul 17, 2006 at 04:01:07PM -0400, Vivek Khera wrote: > > On Jul 17, 2006, at 3:34 PM, Erwin Lansing wrote: > > >On Mon, Jul 17, 2006 at 03:14:48PM -0400, Vivek Khera wrote: > >> > >>>Description: > >>RT 3.6 is now released, and that's what I use. I no longer wish > >>to be responsible > >>for the older rt34 port. > >> > >>>Fix: > >>Please set MAINTAINER in www/rt34 to ports@freebsd.org. I am only > >>maintaining > >>the new version of RT now. Thanks! > > > >How about marking DEPRECATED and set an expiration date as well? > > There are folks who will need it for a while and cannot upgrade > immediately (like with older FreeBSD releases...) so I don't know > what a good expiration date would be. > > I don't know when Best Practical will stop supporting it. > > Perhaps someone else will pick it up? > > If it is marked for expiration, can it be rescued by someone who is > willing to maintain it? If so, then I'm all for expiring it away > after a long period, perhaps a year. > The best would probably be to mark it DEPRECATED pointing to the newer version but not set an EXPIRATION_DATE. That will prevent new users from installing it while keeping support for old users. -- Erwin Lansing http://droso.org Security is like an onion. (o_ _o) It's made up of several layers \\\_\ /_/// And it makes you cry. <____) (____> erwin@lansing.dk