We provide support (bugfixes, workarounds) for releases of JobScheduler and JADE for two years.
The End of Support for product releases is (as of May 2014) as follows:
Releases
clash1. "wikitable" style"text-align:center"
Release |
Support for most recent release |
Note |
||
---|---|---|---|---|
Version Number |
Build Number |
Release Date |
End of Support |
|
1.3 |
3142 |
May 2013 |
April 2015 |
Development frozen, bugfixes will be provided to commercial customers (see below). |
1.5 |
4014 |
Jan 2014 |
Dez 2015 |
Development frozen, bugfixes will be provided to commercial customers (see below). |
1.6 |
4131 |
May 2014 |
April 2016 |
Current version - Release 1.6.4131 was last planned general release for all users. Development now (May 2014) frozen, bugfixes will be provided |
1.7 |
4189 |
June 2014 |
June 2016 |
We will be supporting all builds of this Version 1.7 general availability release for two years from the release of the first build - i.e. until 30th June 2016 |
Note: Bugfixes will be provided to commercial customers until the End of Support date as long as the operating system which the product is running on is supported by the original manufacturer.
Note also:
- We make formal announcements of the End of Support for specific releases at the same time as we announce new releases in our Product News.
- Note that you can subscribe to our Product News with an RSS feed or follow us on twitter.
Operating Systems
clash1. "wikitable" style"text-align:center"
Operating System |
Distribution / Version |
Architecture |
Last JobScheduler/JADE Release Number |
Note |
---|---|---|---|---|
AIX |
5 |
PowerPC |
1.3.12.3192 |
|
SunOS (Open Solaris) |
9 |
x86 |
1.3.12.2341 |
|
Solaris |
9 |
SPARC |
1.3.12.3281 |
|
Windows |
XP (SP1) |
32 bit |
1.3.11 |
For a detailed list of supported platforms see the FAQ: Which platforms is JobScheduler available for and what platform support is provided?
Version Support
Version Support is a service for enterprise customers that provides bug-fixes for a specific product release stand for a period of up to two years after the General Availability release.
- Target Audience
- SOS provides this service to customers who run SOS products in a stable production environment.
- SOS is aware of the fact that companies with large data centres and proven IT processes for change management would not necessarily adhere to the well-known open source paradigm, "release early, release often". Instead, such companies often operate with product release cycles that are as long as possible - which can translate to, "as long as it doesn't break".
- Scope
- SOS Version Support provides enterprise customers with releases for two years, starting from the general availability date.
- General availability releases are usually the first release with a given major or minor version number, i.e. version 1.7.0 which replaces version 1.6.x.
- Ongoing bug-fix releases for a major / minor versions are counted as 1.7.1, 1.7.2, 1.7.3 etc.. From version 1.7.0 onwards, and in contrast with practice is up to and including version 1.6.x, such bug-fix releases will not contain improvements or new features but will be restricted to bug-fixes, ensuring compatibility of the release to its predecessor as closely as possible.
- SOS Version Support maintains source code for all components of a particular release incl. set-up procedures for the 2 year Version Support period.
- Should a critical error be detected in a release then SOS would fix that bug in a way that does not require complete testing of the release. Testing could be reduced to the bug-fix, instead of a full test of the scheduling environment. In such cases SOS would apply the bug-fix to the latest minor version of that release, e.g. 1.7.3.
- SOS Version Support provides enterprise customers with releases for two years, starting from the general availability date.
- Charging model
- Such an individual service requires substantial effort and time from our side.
- Therefore we charge for this service according to the effort required. A three day effort for fixing bugs, building a new release, perform testing and deploying the release to the customer is a good estimate. This effort will be invoiced in addition to the product maintenance fee. Our goal is to keep maintenance fees for customers with standard requirements as low as possible and to provide such additional services to enterprise customers should the need arise.
For more information about SOS Version Support please contact our sales department.