AppSuite:Versioning and Numbering: Difference between revisions
From Open-Xchange
Line 197: | Line 197: | ||
|- | |- | ||
|Open-Xchange would like to provide you with early notification of an upcoming name change for one of our modules, OX Files. As part of our product strategy we are currently developing clients for different desktop and mobile devices to provide improved file handling and synchronization. During development it became clear that a change of name would better reflect customer expectations of the features and functionality provided by OX Drive and provide greatest consistency and clarity for users across devices. The name change from OX Files to OX Drive is planned for January 2014. | |Open-Xchange would like to provide you with early notification of an upcoming name change for one of our modules, OX Files. As part of our product strategy we are currently developing clients for different desktop and mobile devices to provide improved file handling and synchronization. During development it became clear that a change of name would better reflect customer expectations of the features and functionality provided by OX Drive and provide greatest consistency and clarity for users across devices. The name change from OX Files to OX Drive is planned for January 2014. | ||
|February 2014 | |OX App Suite v7.4.2, planned in February 2014 | ||
|- | |- | ||
|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 | |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 |
Revision as of 08:44, 22 January 2014
Versioning and Numbering of Open-Xchange Products
Abbreviations
The Open-Xchange versioning 2009 (After SP5 Update 1) 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.0 |
<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.0.1 |
<build number> | The Rev-number (Revision) shows the progress of the development in single steps | OX App Suite v7.0.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:
|
Release Levels of Open-Xchange
These are the new Open-Xchange Release Levels 2011:
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 | Every 6 to 12 weeks | 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
2007
2008
2009
2010
2011
2012
2013
2014
Please Note: Minor and Major Product Releases in bold
Maintenance expires
Product-, Release- and Component Name | Maintance expires |
---|---|
Open-Xchange would like to provide you with early notification of an upcoming name change for one of our modules, OX Files. As part of our product strategy we are currently developing clients for different desktop and mobile devices to provide improved file handling and synchronization. During development it became clear that a change of name would better reflect customer expectations of the features and functionality provided by OX Drive and provide greatest consistency and clarity for users across devices. The name change from OX Files to OX Drive is planned for January 2014. | OX App Suite v7.4.2, planned in February 2014 |
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 | OX App Suite v7.6.0, planned in April 2014 |
Open-Xchange will discontinue OX App Suite web frontend support for Internet Explorer 9 with the major release of OX App Suite v7.6.0, planned for April 2014. Starting with this release Open-Xchange will officially support Internet Explorer 11. | OX App Suite v7.6.0, planned in April 2014 |
Open-Xchange will discontinue 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, planned for April 2014. | OX App Suite v7.6.0, planned in April 2014 |
Open-Xchange will discontinue 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, planned for April 2014. Further information about the supported platforms are available at http://oxpedia.org/wiki/index.php?title=AppSuite:OX_System_Requirements#Mobility_Solution_-_Supported-_Platforms.2C_Features_and_Devices | OX App Suite v7.6.0, planned in April 2014 |
What version do I have installed
Check this article to find out.