public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Karl Trygve Kalleberg <karltk@prosalg.no>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] stable and unstable branches.
Date: Tue, 23 Jul 2002 22:21:02 +0200 (MET DST)	[thread overview]
Message-ID: <Pine.LNX.3.96.1020723221318.17199C-100000@pluto.prosalg.no> (raw)
In-Reply-To: <3D3DB74A.1000802@fastwebnet.it>


On Tue, 23 Jul 2002, Stefano Peluchetti wrote:

> It also should be really easy to implement thanks to the possibility to 
> select different profiles.

We're slowly introducing the concept of "Quality Assurance" into the
Gentoo development process. 

This is a time-consuming process, of which a split into stable/unstable is
but a small part (although probably the one that will be most visible to
the users). 

In exactly what form such a split will manifest itself is still not know,
but rest assured we're working on it.


For now, to avoid any disappointments wrt stability, think of Gentoo as
"bleeding-edge".


Kind regards,

Karl T



  reply	other threads:[~2002-07-23 20:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-23 20:06 [gentoo-dev] stable and unstable branches Stefano Peluchetti
2002-07-23 20:21 ` Karl Trygve Kalleberg [this message]
2002-07-23 20:58   ` Terje Kvernes
2002-07-23 21:31 ` Christian Bartl
2002-07-23 22:12   ` [gentoo-dev] stable and unstable branches. (auto-bug reports???) Stefano Peluchetti
     [not found]     ` <20020724001127.GC10394@athlon.dolly-llama.org>
2002-07-24  9:28       ` Stefano Peluchetti
2002-07-24  4:32   ` [gentoo-dev] stable and unstable branches Christian Axelsson
2002-07-24  5:28     ` Chad M. Huneycutt
2002-07-24  8:50     ` Alexander Gretencord
2002-07-24 15:32   ` Fredrik Jagenheim

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=Pine.LNX.3.96.1020723221318.17199C-100000@pluto.prosalg.no \
    --to=karltk@prosalg.no \
    --cc=gentoo-dev@gentoo.org \
    --cc=karltk@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