Re: Running testing? -- read this.

On Thu, 2008-06-05 at 01:11 +1200, Chris Bannister wrote:
----- Forwarded message from Manoj Srivastava <srivasta@xxxxxxxxxx> -----

User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) (x86_64-unknown-linux-gnu)
From: Manoj Srivastava <srivasta@xxxxxxxxxx>
Date: Tue, 03 Jun 2008 12:14:03 -0500
To: debian-devel@xxxxxxxxxxxxxxxx
Subject: Re: Bug#484129: release.debian.org: packages in tasks should be fixed in priority and removed in last resort after
discussion
SNIP

OK, my two cents worth: Testing is for testing. If you are not
testing, you don't run it. Testing is NOT meant to be a working
release, never has been. Nobody cares if Testing is broke. They will
fix it. But it will bet fixed when they have the fix for it: no one
will loose sleep over the non-functioning of Testing (except for the
user trying to use Testing as his/hers workstation).

Now the above is my observation, not the Debian policy.

see: http://www.us.debian.org/releases/ and
http://www.us.debian.org/doc/FAQ/ch-ftparchives#s-testing for the
official Debian policy. Joey Hess has said on this list that in his
experience Testing was seldom broke and seldom for any length of time
and should work as a desktop for most people (Joey Hess is one of the
Debian Developers).

Any time you leave Stable, you leave all promise behind that Debian will
work. I run Sid or Ubuntu. Sid has only become unusable for me only
once (PAM broke during an update). If you insists on running Testing OR
Unstable there is one program you MUST run: apt-get apt-listbugs you
have to read the output before proceeding to any updating. This will
save your bacon.

HTH
--
Damon L. Chesser
damon@xxxxxxxxxx
http://www.linkedin.com/in/dchesser

Attachment: signature.asc
Description: This is a digitally signed message part