AppSuite:Versioning and Numbering

Versioning and Numbering of Open-Xchange Products

Abbreviations

The Open-Xchange versioning 2015 will be structured in the following way:

<generation>.<major release>.<minor release> Rev<build number>

Abbreviation	Meaning	Comparison
<generation>	The first number is the product generation number. A new generation may contain new architecture, different technology and many more.	OX App Suite 7
<major release>	The second version number (major release) indicates significant program changes in terms of added functionality. Major changes to design and enhancements of APIs are possible. All APIs shall be backward compatible, which means, that mainly new functions can be added. If Open-Xchange releases a new major release this will be an even number, unstable interim releases have odd numbers.	OX App Suite v7.6
<minor release>	The third version number (minor releases) indicates an update with consolidated bug fixes and non-intrusive feature enhancements. APIs and database will not be changed if this can be avoided. All changes must be backward compatible.	OX App Suite v7.6.1
<build number>	The Rev-number (Revision) shows the progress of the development in single steps	OX App Suite v7.6.1-Rev3
Public Patch Release / Patch Release	A Public Patch Release enables Open-Xchange to publish a feature together with a patch. This in turn enables Open-Xchange to react more flexibly to time requests for certain features, thus relieving minor releases and making it possible to shift them. Delivering a feature with a Public Patch Release requires: It can be implemented without far-reaching side effects. This is especially true for features that are implemented as plug-ins. To a limited extend, features affecting a limited sub set of core functionality can be included. Technical pragmatism is fine to reach the goal (e.g., copy & paste of functionality instead of abstraction into a service). This pragmatism has to be leveled out though as soon as the feature is ported into a more flexible branch. It can be deactivated and is deactivated by default. If a customer installs a Public Patch Release, the familiar feature set does not change. Only if explicitly activating the enhanced features, will they be available to the end user. If features require changes to the data base schema or configuration files, they have to be developed in such a way that they do not impair the running system. Side-effects of Public Patch Releases are evaluated by the respective developers. Together with the QA team, they make a test plan for checking for those side effects and other effects.

Release Levels of Open-Xchange

OX Release Level (new)	New Generation	Major Release	Minor Release	Patch Release	Public Patch Release
Target Audience	All	Public/All	Maintenance customers & Partners	L3 Support Customers, Value Package Partners	Public/All
Purpose	Provide new technologies	Provide functional enhancements including Bug Fixes, accumulate earlier Patch Releases's/ major releases	Provide common bug fixes for all customers, accumulate previous Patch Release's	Provide fixes for severity level 1/2 tickets, for a specific Support Customer, small features, temporary until next Maintenance Release accumulative	Provide fixes for severity level 1/2 tickets, for all Support Customer, small features, temporary until next Maintenance Release accumulative
Frequency	Open-Xchange Roadmap	Decided by Open-Xchange	Decided by Open-Xchange	According to SLA	As soon as required
Support Committment	5 years after First Customer Shippment (FCS)	6 months after FCS (Latest Minor Release at the Major-Release cycle will be official supported)	Last Minor Release of a supported Major Release	Next (Public) Patch Release	Next Public Patch Release
Requested by	Product Management	Product Management, Professional Services	Support, QA, Product Management, Professional Services	Entitled Customer (Support, Professional Services)	Entitled Customer (Support, Professional Services), Product Management
Compatibility requirements/backward compatibility		Database updates, Changes of configuration files	Backward compatibility to last major release. In urgent cases there could be database updates or configuration file changes	Backward compatibility to last major release	Backward compatibility to last major release
Test Efforts OX (QA)	Smoke Tests, Always Tests, Bug Fix Tests, Feature Tests, Dependencies Tests, Heuristic Tests, Performance Tests	Smoke Tests, Always Tests, Bug Fix Tests, Feature Tests, Dependencies Tests, Heuristic Tests, Performance Tests	Smoke Test, Always Tests, Bug Fix Tests, Dependencies Tests, Heuristic Tests, Performance Tests	Smoke Tests, Always Tests, Bug Fix Tests - Support: Fix Approval	Smoke Tests, Always Tests, Bug Fix Tests - Fix Approval
Test Efforts Customer/Partner	Smoke Tests, Bug Fix Tests, New Feature Tests, Integration Tests	Smoke Tests, Bug Fix Tests, New Feature Tests, Integration Tests	Smoke Tests, Bug Fix Tests, Integration Tests	Smoke Tests, Bug Fix Approval	Smoke Tests

Open-Xchange Server 6

Editions

Abbreviation	Description	Target usage
OX:HE	Open-Xchange Hosting Edition	Designed for organizations that want to provide a scalable, multi-tenant e-mail and collaboration solution to their customers. Focus: Software-as-a-Service offerings
OX:SE	Open-Xchange Server Edition	Designed for medium and large size organizations, educational institutions and public administrations seeking a customizable communication solution. Focus: System Integrators
OX:SEforUCS	Open-Xchange Server Edition for Univention Corporate Server	Integration to in-house customer environments

Open-Xchange App Suite

Editions

Abbreviation	Description	Target usage
OX App Suite	Open-Xchange App Suite Community Version	Need to revitalize business growth and increase your competitive advantage? OX App Suite integrates smoothly into existing infrastructures and massively scales across multi-tenant architectures securely and reliably. Offer your users a seamless messaging experience to deliver branded, app-economy services and take back the user experience. German engineered and designed for a mobile world, OX App Suite uses open API's to deliver device independent access to email and messaging, social collaboration and digital media via a rich web-based interface. Through a modular App-based portal, HTML5 interoperability gives providers a new basis to up-sell and cross-sell white-labeled services and mobile applications.

Releases

2016

Please Note: Minor and Major Product Releases in bold

GA	Product	Major Release	Minor Release	Public Patch Releases	Shipped Packages
2016-01-13	OX App Suite v7.6.2, OX 6 Backend v7.6.2 and Connector for Business Mobility				Open-Xchange App Suite / OX 6 Middleware (backend) v7.6.2-rev45 Open-Xchange App Suite frontend v7.6.2-rev35 Open-Xchange EAS v7.6.2-rev20
2016-01-13	OX App Suite v7.6.3, OX 6 Backend v7.6.3, OX Updater and Connector for Business Mobility				Open-Xchange App Suite / OX 6 Middleware (backend) v7.6.3-rev3 Open-Xchange App Suite frontend v7.6.3-rev3 Open-Xchange EAS v7.6.3-rev3 Open-Xchange OX Updater v7.6.3-rev3
2015-01-12	OX App Suite / OX 6 Backend v7.6.1				Open-Xchange App Suite / OX 6 backend v7.6.1-rev14 Open-Xchange App Suite frontend v7.6.1-rev11 Open-Xchange Documentconverter v7.6.1-rev7

Current Product Version Matrix

Open-Xchange products comprise of two major components: Front End and Back End. Each of these components can be rev’ed independently of each other. The following table shows the most recent combinations of Front End version and Back End version that make up a complete product version.

OX App Suite

Version	Backend	Frontend
v7.8.0	v7.8.0-rev12	v7.8.0-rev13
v7.6.2	v7.6.2-rev45	v7.6.2-rev35
v7.6.3	v7.6.3-rev3	v7.6.3-rev3

Open-Xchange Server 6

Version	Backend	Frontend
v7.8.0 / v6.22.10	v7.8.0-rev12	v6.22.10-rev7
v7.6.2 / v6.22.9	v7.6.2-rev45	v6.22.9-rev16
v7.6.3	v7.6.3-rev2	v6.22.9-rev16

Please Note - Additional Information

Product-, Release- and Component Name	Additional Information
LinkedIn Integration	Regarding the integration between OX App Suite and LinkedIn, we would like to notify you about an upcoming LinkedIn API change, which is used by the App Suite app server. We were informed by LinkedIn this week that LinkedIn will restrict access to parts of their currently available API for all existing users and partners by May 15th. LinkedIn will only allow access to the full API, if you sign up for the LinkedIn partner program. Read More: Open-Xchange Forum
Facebook Integration	Facebook has introduced a new API Permission called “read_stream”, which allows clients of their API to retrieve the Facebook stream of a user. This data was used in the OX App Suite Portal widget to give users instant access to their Facebook data without leaving App Suite. The issue with this new API permission is that Facebook only grants it to 3rd party applications which do not run on the following platforms (All platforms where Facebook already is present): Web, TV, iOS, Android, In-Car. Read More: Open-Xchange Forum
T-Online Integration	Regarding the integration between App Suite and the social network T-Online, we would like to notify you about an upcoming T-Online change, which is used by the App Suite app server. As a result of the change from a clickable HTML page to a single-page-javascript application, the Open-Xchange App Suite Integration for T-Online will stop working and removed.

Maintenance expired (Archive)

Product-, Release- and Component Name	Maintance expired
Open-Xchange will discontinue support for Apple iOS 7 with the next major release of OX App Suite v7.8.0	Since OX App Suite v7.8.0: 2015-10-07
Open-Xchange will discontinue support for Debian Squeeze (Debian 6) with the next major release of OX App Suite v7.8.0. We encourage administrators to update to the latest operating system version of Debian.	Since OX App Suite v7.8.0: 2015-10-07
With the v7.8.0 release, Open-Xchange will discontinue support for the Random Token login method (sometimes also called Easy Login). Specifically, this means that the "login?action=redirect" call (see http://oxpedia.org/wiki/index.php?title=HTTP_API#Redirect) will be removed. Furthermore, the "com.openexchange.ajax.login.randomToken" setting will be removed from the "login.properties" file, and the "login?action=login" call will never contain the "random" token. We strongly encourage users of the Random Token login method to change their custom login implementations and use one of the supported methods.	Since OX App Suite v7.8.0: 2015-10-07
Open-Xchange discontinues support for Apple Mac OS X 10.8 Mountain Lion with the minor release of OX App Suite, v7.6.2: 2015-03-11	Since OX App Suite v7.6.2: 2015-03-16
Open-Xchange discontinues support for Apple iOS 6 with the minor release of OX App Suite, v7.6.2	Since OX App Suite v7.6.2: 2015-03-16
Open-Xchange discontinued support of all old Android stock browsers on mobile and tablet devices with the release of OX App Suite v7.6.1. OX App Suite is only supported on the new official stock browser, Chrome on Android.	Since OX App Suite v7.6.1: 2014-10-15
Support for AJP based communication between the HTTP server and the OX backend server. Open-Xchange already provides a new HTTP connector which is based on the Grizzly project. Download and configuration instructions are available at http://oxpedia.org/wiki/index.php?title=AppSuite:Grizzly	Since OX App Suite v7.6.0: 2014-06-25
Open-Xchange discontinued OX App Suite web frontend support for Internet Explorer 9 with the major release of OX App Suite v7.6.0.	Since OX App Suite v7.6.0: 2014-06-25
Open-Xchange discontinued Open-Xchange Server 6 and OX App Suite calendar and contact synchronization (CalDAV/CardDAV) support for Mac OS X 10.6 (Snow Leopard) and Mac OS X 10.7 (Lion) with the major release of OX App Suite v7.6.0.	Since OX App Suite v7.6.0: 2014-06-25
Open-Xchange discontinued Connector for Business Mobility support for Windows Mobile 6, 6.5, Symbian (Mail for Exchange 3.x), Apple iPhone iOS 5 and Blackberry with the major release of OX App Suite v7.6.0.	Since OX App Suite v7.6.0: 2014-06-25
With OX App Suite v7.4.2, the name of the “Files” app was changed to “Drive”. As part of our product strategy we developed clients for different desktop and mobile devices to provide improved file handling and synchronization.	Since OX App Suite v7.4.2: 2014-02-11
Debian 7 (Wheezy) was released by the Debian project on May 4th 2013. Both OX App Suite and Open-Xchange Server 6 support Debian 7 with OpenJDK 7 and MySQL 5.5 with this release of OX App Suite. Please note that the combination Debian 7 / OpenJDK 6 or Sun Java 6 will not be supported as a platform by Open-Xchange.	Since OX App Suite v7.4.0: 2013-09-26
Open-Xchange discontinued support for the currently available "showruntimestats" monitoring function (which fetches runtime information from the Java virtual machine and about the Open-Xchange Groupware backend). With OX App Suite v7.4.0, there is a new monitoring function using Jolokia for Open-Xchange. From v7.4.0 onwards, this is located inside the Open-Xchange Bundle and configured by jolokia.properties. Further information can be found at http://oxpedia.org/wiki/index.php?title=Jolokia	Since OX App Suite v7.4.0: 2013-09-26
Open-Xchange provided a new LDAP Contact Storage Integration Bundle. Open-Xchange discontinued support for the old bundle with OX App Suite v7.2.1. Further configuration information is available at the Open-Xchange Knowledgebase under: http://oxpedia.org/wiki/index.php?title=ContactStorageLDAP	Since OX App Suite v7.2.1: 2013-05-27

What version do I have installed

Check this article to find out.