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!
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? -erwin -- Erwin Lansing http://droso.org Security is like an onion. (o_ _o) It's made up of several layers \\\_\ /_/// erwin@FreeBSD.org And it makes you cry. <____) (____> erwin@aauug.dk
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.
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
State Changed From-To: open->closed Committed, thanks!