This minimal period ensures the package has been tested and gives enough time to users to file bugs if the package is suffering from problems. They upload their packages in the unstable distribution.įrom there packages trickle to the testing distribution once they satisfy some quality checks: they must not have new release-critical bugs, they must have been built on all architectures that were previously supported, they must not break any dependency in testing, and they must have spent at least 10 days in unstable. Updating packages, working on release goalsĭuring most of the cycle, developers work on packaging new upstream versions and implementing release goals. In the Debian archive, testing is just a symbolic link pointing to the right directory (squeeze currently). Its codename is decided by the release managers and there’s a tradition of picking a character’s name from the Toy Story movie.Īs an example, the “wheezy” distribution will be created once “squeeze” (aka Debian 6.0) is out.įor simplicity there’s a generic name to refer to the distribution used to prepare the next stable release: it’s testing. Its initial content is a copy of the (just released) stable distribution. Immediately after a stable release, a new distribution is created in the Debian archive. ![]() This article gives a short overview of the process leading to the next stable release. Those release come out approximately every 18-24 months. ![]() Currently, the main product of the Debian project is its stable release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |