From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3091 invoked from network); 2 Jul 2004 02:17:39 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 2 Jul 2004 02:17:39 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BgDcQ-0006Wf-Og for arch-gentoo-dev@lists.gentoo.org; Fri, 02 Jul 2004 02:17:38 +0000 Received: (qmail 15255 invoked by uid 89); 2 Jul 2004 02:17:38 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 20433 invoked from network); 2 Jul 2004 02:17:37 +0000 X-Authentication-Warning: rocky.richmond.edu: apache set sender to spyderous@gentoo.org using -f Message-ID: <43062.205.241.48.33.1088734649.squirrel@spidermail.richmond.edu> Date: Thu, 1 Jul 2004 22:17:29 -0400 (EDT) From: "Donnie Berkholz" To: In-Reply-To: <40E4B84B.1040501@scms.waikato.ac.nz> References: <40E4B84B.1040501@scms.waikato.ac.nz> X-Priority: 3 Importance: Normal Cc: X-Mailer: SquirrelMail (version 1.2.10) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MailScanner-SpamxCheck: , X-MailScanner-From: spyderous@gentoo.org X-MailScanner: Found to be clean Subject: Re: [gentoo-dev] Policy for retirement of old gentoo 'versions' X-Archives-Salt: 1441abd0-7a1d-4d51-be52-42ed9f5dd6c0 X-Archives-Hash: 2417150b4c1d104c0e9a2d6443782767 Barry Shaw said: > Is there any policy/ideas/consensus among developers about how long a > particular "version" will remain supported in portage? If not, it might > be a useful idea to set sunset dates for particular "versions" of gentoo > (as I doubt they are all going to be supported indefinitely). If there > is a clear end date, it prevents anyone being caught out unexpectedly. I generally keep a minimum of two ebuilds in, so testing for a newly introduced problem is easier. If I put out seven ebuilds in two weeks for some ungodly reason, I don't expect to be maintaining some sort of minimum lifetime for each ebuild -- just the newest two will stick around. We have no policy stating a minimum support lifetime for any given version right now (AFAIK, of course), despite a push for it amidst emphasis for Gentoo in the enterprise. Donnie -- gentoo-dev@gentoo.org mailing list