Download methods:

• Tarballs - snapshot, preview, release, lts
• Git - indev
• Mirrors - indev

Release cycle:

• Once an indev branch is both stable with passing tests and has a meaningful feature difference compared to the last snapshot, it is packaged as a snapshot. Snapshots are named by the dates. Indevs are not named.
• Once an indev branch hits the intended features for the next release, it is packaged as a preview. Previews are named by the release they may become followed by a period and the preview number they are.
• Once a preview has received an audit and stability patches, it is packaged as a release. Releases are named by the release number. Release builds are not modified after the initial packaging. Releases contain prebuilt binaries.
• Some releases are chosen for LTS, where they receive regular audits. LTS versions do not receive new features, only patches from the audits and backports from indev for bug and security fixes. LTS releases are named by the release name they come from with a dot followed by the patch / audit number. LTS builds contain prebuilt binaries. Once an LTS is deprecated, it will have -DEP added to the end of the version tag.