public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Policy for retirement of old gentoo 'versions'
Date: Fri, 02 Jul 2004 08:48:35 -0400	[thread overview]
Message-ID: <1088772514.16422.39.camel@localhost> (raw)
In-Reply-To: <43062.205.241.48.33.1088734649.squirrel@spidermail.richmond.edu>

[-- Attachment #1: Type: text/plain, Size: 2172 bytes --]

On Thu, 2004-07-01 at 22:17, Donnie Berkholz wrote:
> 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.

As Donnie said, there is no policy laid out.

In general, I will keep 2 versions in portage.  Usually it is a stable
version, and a testing version.  Depending on the ebuild, I will leave
more versions.  For example, look at PXES or VMware Workstation.  PXES
is something that would be in use and probably not easily upgraded for
everyone, so I have left every stable version in portage since I added
the package.  VMware Workstation is a licensed product, so I leave one
version per license in the tree (3.x and 4.x).  There are currently 2
4.x ebuilds simply because one is still in testing.

Then you have packages like gcc/glibc, which usually stay in the tree
for much, much longer.

With an enterprise version of Gentoo, there will need to be much more
help in maintaining certain packages, simply because patches will need
to be back-ported to older versions and other such headaches that most
other distributions must deal with.

Right now, we simply don't have the manpower to keep up with such
things, which is why we do not make things version dependent, where
possible.

-- 
Chris Gianelloni
Release Engineering QA Manager/Games Developer
Gentoo Linux

Is your power animal a penguin?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-02 12:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-02  1:20 [gentoo-dev] Policy for retirement of old gentoo "versions" Barry Shaw
2004-07-02  2:17 ` [gentoo-dev] Policy for retirement of old gentoo 'versions' Donnie Berkholz
2004-07-02 12:48   ` Chris Gianelloni [this message]
2004-07-02 13:44     ` William Kenworthy
2004-07-02 14:41       ` Grant Goodyear
2004-07-02 15:15         ` Dylan Carlson
2004-07-02 20:29           ` Chris Gianelloni
2004-07-02 21:06             ` Dylan Carlson
2004-07-02 21:37               ` Chris Gianelloni
2004-07-03  6:34                 ` Dylan Carlson
2004-07-04 22:10                   ` Marius Mauch
2004-07-05  1:14                     ` Dylan Carlson
2004-07-04 22:16                   ` Barry Shaw
2004-07-05  1:01                     ` Dylan Carlson
2004-07-05  2:19                       ` Barry Shaw
2004-07-02 20:21       ` Chris Gianelloni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1088772514.16422.39.camel@localhost \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox