Our release branches are modeled after Debian and Ubuntu.
Recommended for dev and testing hosts.
This is where our maintainers upload packages to once they consider them ready for distribution. A number of automated checks are run on the packages to catch common packaging issues and to ensure formal correctness. This is where you will find recent applications and ongoing enhancements. On the flipside, there is a chance for defects. Updates are frequent.
As of 2012, recommended for dev and testing systems.
This is where packages from “unstable” move to. This allows us to catch and handle defects which can occur in “unstable” before they move to “testing”. Package propagation is carried out manually, but is subject to automation. Once implemented, updates should happen frequently. Currently, updates are infrequent, one every two to four weeks.
As of 2012, dublin is recommended for production systems.
While “testing” is a moving target, it also resembles the basis for a named release towards which we work. Once a set of goals has been reached, we freeze “testing” and continue to provide it under its release name. The named release which we are currently working on is named: “kiel”. Previous named releases: dublin.
Do not use!
This is an early release which pre-dates our current release model. It has not seen updates in years and will never have.