There are separate release branches that you can choose as your primary source for CSW packages. These branches address different demands on package update frequency and package stability and are similar in nature to what you might be accustomed to in Debian GNU/Linux or Ubuntu.
Unstable
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.
Testing
This is where packages from “unstable” move to in a delayed manner. 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. Also known as: “current”.
Named Releases
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: “dublin”. Previous named releases: none.
Legacy
This is an early release which pre-dates our current release model. It has not seen updates in years and should be considered dead. Also known as: “stable”.
