With millions of ownCloud users, there are a wide variety of needs and requirements. We offer Release Channels to give our users more flexibility in choosing an ownCloud version to meet their needs. Below you can find and pick the best Channel for you.

You can choose a channel of your preference in the Administrator settings in your ownCloud instance if you have installed ownCloud from an archive. If you prefer using Linux packages, you can pick a repository for a specific version, a repository with daily snapshots or follow the repository which always has the latest stable feature release.

NOTE that you can only upgrade to a newer version. Skipping major versions when upgrading and downgrading to older versions is not supported by ownCloud.

  Release channel   Use case   Get it here

Production

This channel delivers the latest fully tested release of ownCloud.
That does not imply that these releases are bug free. The issues are known and can be worked around. The downside of this channel is that the releases are behind in terms of features and performance.
Older archives are available from our changelog.
Production repositories are available for the following major versions: 9.0 (new since 9.0.1), 8.2, 8.1 and 8.0
Register and activate one of these repositories with your package manager to get updates within the same major version*

Stable

This channel delivers the latest feature releases ready for home users at minimal risk. Archive File (MD5)
Linux Packages

Beta

Betas and release candidates are the versions of choice for testers in preparation for an ownCloud release. They provide a short-term-stable point to report bugs against. Grab these to make sure the upcoming release works well on your infrastructure.
Automatically generated snapshot tarballs and packages track daily ownCloud development. These are suitable to check if bugs are fixed but can break any time.
Follow our testpilots mailing list to get the latest test version.
Linux Packages

Daily

Daily builds are meant to reproduce bugs as well as to enable testers to follow the development of the next major version. Archive File (MD5)
Linux Packages

If you are looking to grab an archive of a specific version or are looking for the version-specific Linux package repositories, you can find links to them in our changelog.

Note that releases don't show up in the updater app right away. We usually stagger releases out to watch the impact and hold off in case very serious problems pop up. In practice, most bugfix releases are available within a week, major releases within a week for the Stable channel and a week after the first bugfix release (for example, 9.0.1) for the Production channel. Packages for the Stable channel are available close by or at the release date, Production also waits for the first minor update after a major release.

Security note:
To receive information about updates and security issues, we recommend a subscription to our low-traffic announcement mailing list.

Warning:
If you pick a specific Linux Package repository rather than following stable, you assume the responsibility for a timely upgrade to a new stable release once your current release is no longer supported. We support releases for a significant time, but not forever, and at some point you have to move to a newer version to continue to receive security and stability improvements.
If at all possible, we suggest to upgrade sooner rather than later. Doing a test on a copy of your production environment is a better way of ensuring the new version works for you than waiting and hoping all issues are found and fixed – that way, you lose out on many of the benefits of the new release, not only in terms of features and user interface enhancements but also when it comes to performance improvements and scalability.

Note that from 8.2 onward, ownCloud packages can be found on download.owncloud.org rather than on the openSUSE Open Build Service. This means you will have to move repositories if you want to upgrade from the Stable 8.1 release.

To upgrade in the safest way possible, always update to the latest minor release before upgrading to a new version. As an extreme example, to upgrade from 7.0 all the way to 9.0, upgrade 7.0.x to 7.0.14, then upgrade to 8.0.13, 8.1.8, 8.2.5, then 9.0.2.

...