Maintenance Cycle for UCS
From Univention Wiki
This article describes the maintenance cycle for Univention Corporate Server. An overview about the Maintenance Cycles can be found in a separate article.
UCS maintenance cycle rules
The following basic rules for the UCS maintenance cycle apply. UCS product versions are divided into major and minor releases.
A major version focuses on fundamental extensions and interfaces may be changed. Example for a major version is UCS 3.
- UCS major versions are published ca. every 3-4 years.
- UCS major versions have a maintenance cycle of at least 5 years.
During its maintenance cycle a major version receives several minor updates through minor versions that are comparable to the Service Packs of Microsoft Windows. Such a minor version focuses on the extension of the product and on bug fixes. Interfaces will only be extended in a compatible way or cleared up upon issues. UCS minor versions allow a simple and automatic update. Example for a minor version is UCS 3.1.
- UCS minor versions are published ca. every 12 months.
- UCS minor versions have a maintenance cycle of at least 1 year.
- The maintenance cycle of a UCS minor version ends 6 months after the release of the following version.
Minor enhancements and fixes for small issues are continually provided by Errata Updates and collected in Patchlevel releases (e.g. UCS 3.1-1). They are public available through the Online-Update in Univention Corporate Server.
- The maintenance cycle of a patchlevel release ends 6 weeks after the release of the following patchlevel.
Maintenance cycle overview
The following table gives an overview about the currently maintained Univention Corporate Server (UCS) versions.
| Product version |
Release date |
Maintenance until |
|---|---|---|
| Major version 3 | ||
| UCS 3.2 | Q4 2013 | |
| UCS 3.1 | Dec 12, 2012 |
|
| UCS 3.0 | Dec 09, 2011 |
|
| Major version 2 | ||
| UCS 2.4 | Aug 31, 2010 |
|
