AppSuite:Version Support Commitment: Difference between revisions

From Open-Xchange
Line 18: Line 18:


=== Minor Releases ===
=== Minor Releases ===
Within a Major Release cycle support is always available for the most recent Minor Release. To provide sufficient time for the update, Open-Xchange will support the two most recent Minor Release (e.g. 7.0.1 and 7.0.2) for four weeks in parallel after the release (FCS) of the most recent Minor Release.
Within a Major Release cycle support is always available for the most recent Minor Release. To provide sufficient time for the update, Open-Xchange will support the two most recent Minor Release (e.g. 7.0.1 and 7.0.2) for four weeks in parallel after the First Customer Shipment (FCS) of the most recent Minor Release.


=== Patch Releases ===
=== Patch Releases ===

Revision as of 09:21, 4 September 2013

Open-Xchange Version Support Commitment

Open-Xchange Versions

A detailed description of the different versions of Open-Xchange can be found in the Support Definitions document included in the contract.

  • New Generation: A new release that may contain major feature changes, new architecture or different technology.
  • Major Release: A major update of Open-Xchange's Product that will normally include all the changes provided by Minor Releases for the current version. They are cumulative so a customer has to install the latest Major Release to benefit from all changes that are available for this Open-Xchange Product. Major Releases also provide functional enhancements. A Licensee is therefor encouraged to install all Major Releases as soon as feasible.
  • Minor Release: A change of Open-Xchange's Product that is released on an as needed basis, containing minor feature enhancements as well as solutions for known problems. Minor Releases go through quality assurance testing and APIs are not changed.
  • Patch Release: A change to Open-Xchange's Product, to temporarily fix a Problem. “Patch Releases” are one-offs, special one-time builds not fully regression tested and/or recertified. The software change will be applied to the next formal Minor- or Major Release of the Software. Patch Releases are cumulative in nature, thus every new Patch Release will contain all former software changes released earlier as Patch Releases for the relevant Minor- or Major Release.
    • Private Patch Release: A Private Patch Release is a Patch Release that is built for a specific customer only.
    • Public Patch Release: A Public Patch Release is a Patch Release which is delivered to all customers.

Support Commitment

Major Releases

A Major Release cycle will be supported 6 Months after First Customer Shipment (FCS) of the following Major Release

Minor Releases

Within a Major Release cycle support is always available for the most recent Minor Release. To provide sufficient time for the update, Open-Xchange will support the two most recent Minor Release (e.g. 7.0.1 and 7.0.2) for four weeks in parallel after the First Customer Shipment (FCS) of the most recent Minor Release.

Patch Releases

Patches are cumulative which means each Patch Release also contains all fixes from the earlier Patch Releases within a Minor Release cycle. Therefore always the latest Patch Release (public or private) will be supported.

Time Bar Example

Support committment overview.png

Open-Xchange Releases Support Commitment

Release FCS Supported Commitment
v6.22.0 2012-10-10 Discontinued Support
v6.22.1 2012-11-14 Discontinued Support
v7.0.0 2012-12-18 Discontinued Support
v7.0.1 2013-02-20 Discontinued Support
v6.22.2 / v7.0.2 2013-03-12 Support Commitment 2013-10-11
v7.2.0 2013-04-11 Discontinued Support
v7.2.1 2013-05-27 Discontinued Support
v7.2.2 / 6.22.3 2013-07-01 Support Commitment