Debian testing [LWN.net]

Debian testing

Posted May 6, 2004 9:47 UTC (Thu) by boomi (guest, #21418)
In reply to: Debian testing by tjc
Parent article: Revealed: how Fedora and the community interact

> Finding out that a package is messed up after it has been installed it isn't all that helpful.
_Someone_ has to find out. If you use unstable, you agree to help discover bugs in new
packages. Use testing if you don't want to do that. Btw: old packages are stored in /var/apt/
archives, you can easily restore an old version.

Using unstable? You are asking for trouble. Which is a good thing, someone else won't have the
problem if you discover _and_ fix or report it. Using full unstable on a remote/production box is
just irresponsible (done that too many times). You can mix stable and unstable packages, no
need to run ssh from unstable.

(Log in to post comments)

Debian testing

Posted May 6, 2004 15:20 UTC (Thu) by tjc (subscriber, #137) [Link]

If you use unstable, you agree to help discover bugs in new packages.

I don't recall entering into any such agreement. :-)

Use testing if you don't want to do that.

Testing is too old for my taste. By the time it becomes stable, it will be nearly obsolete. It's sort of the worst of both worlds in that respect.

There's a big gap between "testing" and "unstable." It's within this gap that Fedora Core and Mandrake exist. Debian could probably increase the size of their user base by a significant amount by filling this gap.

Personally, I use "unstable" on my workstation, but I keep a partition with Fedora Core around in the event that "unstable" becomes too much of an adventure. I wait for the dust to settle, and come back in a week or so. This happens about once a year.

Debian testing

Posted May 10, 2004 9:55 UTC (Mon) by mbanck (subscriber, #9035) [Link]

There's a big gap between "testing" and "unstable."

I don't believe this is true right now. The release team is doing a great job nowadays resolving problems in testing when two packages keep each other out and so. It used to be quite bad when only AJ was looking after testing, but since we have a couple of very bright "Release Lieutenants", things are moving quite well.

For example, it used to take a new glibc package months to enter testing. Last week, 2.3.2.ds1-12 entered testing after being in unstable for just two weeks or so.

I agree that stable might be too old for desktop use (I have to use it myself at work), but testing is only lacking behind only for some corner-cases, while it is quite uptodate in general.

Michael