The PureOS repositories consist of [[ https://master.pureos.net/depcheck/ | various archive sections, so-called "suites" ]]: - **landing** - **green** - **purple** - **laboratory** Packages in the **green** suite are visible to the users of PureOS and are the current rolling release distribution. The **landing** suite however contains packages not yet fit for being published in **green**. The **landing** suite is synchronized with Debian Testing (thus PureOS being based on Debian and has rolling release nature because of testing suite). Every package uploaded to PureOS needs to pass through **landing** before reaching **green**. Packages are automatically moved from **landing** to the release suite if they meet the following criteria: * Contain no known bugs * Are installable and do not make the target suite more broken. This includes: - Being built on all main architectures - Having dependencies available - Being installable * Have been in **landing** for at least a 6 hours If everything is fine with your packages, you can be certain that it will be in green at least 24 hours after your upload.

The PureOS repositories consist of [[ https://master.pureos.net/depcheck/ | various archive sections, so-called "suites" ]]: - **landing** - **amber** - **byzantium** Packages in the **byzantium** suite are visible to the users of PureOS and are the current rolling release distribution. Packages in the **amber** suite are visible to the users of PureOS and are the current stable distribution. The **landing** suite however contains packages not yet fit for being published in **byzantium**. The **landing** suite is synchronized with Debian Testing (thus PureOS being based on Debian and has rolling release nature because of testing suite). Every package uploaded to PureOS needs to pass through **landing** before reaching **byzantium**. Packages are automatically moved from **landing** to the release suite if they meet the following criteria: * Contain no known bugs * Are installable and do not make the target suite more broken. This includes: - Being built on all main architectures - Having dependencies available * Have been in **landing** for at least a 6 hours (There are sometimes shorter waits for certain packages.) If everything is fine with your packages, you can be certain that it will be in amber of byzantium at least 24 hours after your upload.

The PureOS repositories consist of [[ https://master.pureos.net/depcheck/ | various archive sections, so-called "suites" ]]: - **landing** - **green**amber** - **purple** - **laboratory**byzantium** Packages in the **green**byzantium** suite are visible to the users of PureOS and are the current rolling release distribution. Packages in the **amber** suite are visible to the users of PureOS and are the current stable distribution. The **landing** suite however contains packages not yet fit for being published in **green****byzantium**. The **landing** suite is synchronized with Debian Testing (thus PureOS being based on Debian and has rolling release nature because of testing suite). Every package uploaded to PureOS needs to pass through **landing** before reaching **green****byzantium**. Packages are automatically moved from **landing** to the release suite if they meet the following criteria: * Contain no known bugs * Are installable and do not make the target suite more broken. This includes: - Being built on all main architectures - Having dependencies available - Being installable * Have been in **landing** for at least a 6 hours (There are sometimes shorter waits for certain packages.) If everything is fine with your packages, you can be certain that it will be in greenamber of byzantium at least 24 hours after your upload.