From: Evan Read <eread@freeshell.org>
To: George Shapovalov <george@gentoo.org>
Cc: gentoo-dev@gentoo.org, mpickers@optusnet.com.au
Subject: Re: [gentoo-dev] State of Developement
Date: Tue, 27 Aug 2002 02:12:35 +0000 [thread overview]
Message-ID: <20020827021235.GB11250@SDF.LONESTAR.ORG> (raw)
In-Reply-To: <200208261524.41211.george@gentoo.org>
On Mon, Aug 26, 2002 at 03:24:40PM -0700, George Shapovalov wrote:
<snip>
> The point I am getting at here is that we should and can allow our users to
> take care of a large portion of non-crytical packages. What we need is:
> 1. Multiple stability levels or KEYWORDS
> 2. Streamlined ebuild processing - that automates submission of new
> ebuilds/versions and assigns them some kind of "new" or "user-test"
> keyword/level
> 3.Feedback system that collects user voices and moves ebuilds to corresponding
> categories increasing or decreasing their stability rating.
> 4. Core group oversees and takes care of the core/crytical stuff and has
> *much* more time to work onportage/sysinit/other_more_distro_specifc_stuff
> Well, that would be one possible point of view on this :).
Keywords, hey? So I could track a stable tree that doesn't change so much
and doesn't break? Is this coming with 1.4?
> 1. multitude of profiles (not just arch/gcc specific but tailored to certain
> tasks: such as server vs desktop, etc.)
Oh sweet ;) desktop+stable? ;)
> And it all takes quite some work, so any help is appreciated; but then any
> exciting project has a lot of routine associated with it.
This sounds good George. I have been evaluating Gentoo of the last few
days and I keep coming back to "it needs a stable tree". I really hate
breakages. I would prolly be willing to test new stuff in VMWare or UML,
but not my main system.
I think that having different, trackable releases would be a turning point
for the distribution. It could become useful for production.
p.s. Is there a page that lists new stuff coming in 1.4?
Thanks!
--
Evan Read
http://eread.freeshell.org
"The future comes 60 minutes an hour no matter who you are or what you
do."
The Screwtape Letters - C.S. Lewis
next prev parent reply other threads:[~2002-08-27 2:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 6:43 [gentoo-dev] State of Developement Paul
2002-08-26 7:21 ` Henti Smith
2002-08-26 10:52 ` Preston A. Elder
2002-08-26 18:01 ` Jeremiah Mahler
2002-08-26 19:28 ` Grant Goodyear
2002-08-26 21:38 ` Dominik Westner
2002-08-26 22:24 ` George Shapovalov
2002-08-27 0:56 ` Daniel Mettler
2002-08-27 3:45 ` George Shapovalov
2002-08-27 14:35 ` [gentoo-dev] 1.4beta compliment, complaint, question, suggestion Fuper
2002-08-27 15:20 ` mike
2002-08-27 20:26 ` Karl Trygve Kalleberg
2002-08-27 2:12 ` Evan Read [this message]
2002-08-27 1:38 ` [gentoo-dev] State of Developement Evan Read
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=20020827021235.GB11250@SDF.LONESTAR.ORG \
--to=eread@freeshell.org \
--cc=gentoo-dev@gentoo.org \
--cc=george@gentoo.org \
--cc=mpickers@optusnet.com.au \
/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