From: "Donnie Berkholz" <spyderous@gentoo.org>
To: <baz@scms.waikato.ac.nz>
Cc: <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Policy for retirement of old gentoo 'versions'
Date: Thu, 1 Jul 2004 22:17:29 -0400 (EDT) [thread overview]
Message-ID: <43062.205.241.48.33.1088734649.squirrel@spidermail.richmond.edu> (raw)
In-Reply-To: <40E4B84B.1040501@scms.waikato.ac.nz>
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
next prev parent reply other threads:[~2004-07-02 2:17 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 ` Donnie Berkholz [this message]
2004-07-02 12:48 ` [gentoo-dev] Policy for retirement of old gentoo 'versions' Chris Gianelloni
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=43062.205.241.48.33.1088734649.squirrel@spidermail.richmond.edu \
--to=spyderous@gentoo.org \
--cc=baz@scms.waikato.ac.nz \
--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