["DebianReleases"] > DebianTesting


Debian testing is the current development cycle of Debian. It's named after the next stable release [:DebianLenny:lenny] (as of May 2007)

inline:Portal/IDB/official-doc.png

[http://www.debian.org/devel/testing] - Official page about Debian Testing.

What is in Testing

A package is installed into the testing dist from [:DebianUnstable:Unstable] automatically when a list of requirements is fulfilled:

These requirements should assure that testing is in a pretty workable state but still developing. Especially when packages get restructured, packages that are not quite releasable get into testing, so not all the fun of using a developmental version is removed.

Considerations

An example of testing's unstableness is the upgrade from perl-5.6.0 to perl-5.6.1 which made perl unable to find its modules if they were from a package built with perl-5.6.0. Setting the environment variable PERL5LIB to /usr/lib/perl/5.6.0 solved the problem.

Testing changes more often than [:DebianStable:stable] , but not as crazily as [:DebianUnstable:unstable]. See also DebianStability.

Testing has the worst security update speed compared to stable and unstable. Don't prefer testing if security is a concern. (is this still valid after 2005-06-06?)

If you were tracking [:DebianTesting:testing] but really meant to be tracking [:DebianEtch:etch], update your /etc/apt/sources.list replacing 'testing' with 'etch'. The 'etch' alias would have tracked 'etch' through it's transition into 'stable'.

You can see what distribution an alias is tracking by looking at the Release file; e.g.:

If you wonder why a package (or a particular version thereof) is not yet in testing, see http://bjorn.haxx.se/debian.

Testing to Stable

How does ''Testing'' becomes the new ''Stable'' release ?
see ["DebianReleaseFAQ"].

See also