Date: Mon, 17 Jul 2006 20:20:22 GMT From: Erwin Lansing <erwin@FreeBSD.org> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/100446: relinquish maintainership Message-ID: <200607172020.k6HKKMLq022067@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/100446; it has been noted by GNATS. From: Erwin Lansing <erwin@FreeBSD.org> To: Vivek Khera <vivek@khera.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200607172020.k6HKKMLq022067>