ownCloud release channels

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 that meets their needs. Below you can find and choose the best channel for your needs.

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 versionSkipping major versions when upgrading and downgrading to older versions is not supported by ownCloud.

 

Release Channel Use Case Latest Versions
Production Production channels offer the latest stable version of an ownCloud product. The version is tested and ready for use in production environments. This version is meant for end users, who use ownCloud to sync and share their real data.

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.

ownCloud server:

tar ball: 10.0.4
Appliance: 10.0.3

Desktop Client:
Mac: 2.4.0
Linux: 2.4.0
Windows: 2.4.0

Have a look on our downloads page for available downloads.

Fresh The “Fresh” release channel offers the latest stable build of a product and provides the newest, production ready version. Although ownCloud puts a lot of effort in quality assurance it is possible that some edge case bugs are not discovered in a fresh release. Those releases are meant for end users who want to have the newest functions in their ownCloud. ownCloud server:

tar ball: 10.0.4

Have a look on our downloads page for available downloads.

Technical Preview Technical preview releases can contain alpha, beta and release candidate versions. Those releases are not meant for production environments but are used to test new versions in the community. Grab them to make sure the upcoming release works well on your infrastructure.

ownCloud encourages you to get involved! Join the community today and sign up for exclusive pre-releases.

See how you can join »

ownCloud server:

tar ball: 10.0.5 tarball tech preview
Appliance:

Desktop Client:
Mac: 2.4.0 RC2
Linux: 2.4.0 RC2
Windows: 2.4.0 RC2

Have a look on our downloads page for available downloads.

Desktop Client “Testpilot Cloud” The test pilot cloud is the ownCloud desktop client in an early test version. The difference from the technical preview is, that this client can be installed parallel to your production client without touching your production data. Latest version for
Linux: 2.4.0 RC2
Windows: 2.4.0 RC2
Mac: 2.4.0 RC2

 

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 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 soon after or at the time of 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 amount of 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 upgrading sooner rather than later. Doing a test on a copy of your production environment is a better way of ensuring that the new version works for you, rather 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.

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 8.2 all the way to 10.0, upgrade 8.2.x to 9.0.9, then upgrade to 9.1.5, then to 10.0.2.