Product Life Cycle
Releases
The End of Life for product releases is (as of Aug 2014) as follows:
clash1. "wikitable" style"text-align:center"
Release |
Product Life Cycle |
Note |
||||
|---|---|---|---|---|---|---|
Maintenance Support Period |
Version Support Period |
|||||
Version Number |
Most Recent Build Number |
GA Date |
Most Recent Release Date |
Last Order Date |
End of Life |
|
1.3 |
3142 |
Sep 2011 |
May 2013 |
May 2013 |
Aug 2014 |
Development frozen, bug-fixes will be provided to commercial customers (see #Version Support below). |
1.5 |
4014 |
Jul 2013 |
Jan 2014 |
Jan 2014 |
Jul 2015 |
Development frozen, bug-fixes will be provided to commercial customers (see #Version Support below). |
1.6 |
4131 |
Jan 2014 |
May 2014 |
|
Jan 2016 |
Current version - Release 1.6.4131 was the last planned general release for all users. Development now (Aug 2014) frozen, bugfixes will be provided to commercial customers (see #Version Support below). |
1.7 |
4189 |
Jun 2014 |
Jun 2014 |
|
Jun 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: Bug-fixes 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?
Product Maintenance Period
Product Support is a service for all customers that provides bug-fixes starting from the General Availability date up to the Latest Public Bug-fix Release.
- Target Audience
- SOS provides this service to all customers with a support contract.
- Scope
- Product Maintenance provides customers with releases after the General Availability date up to the end of the Maintenance Period.
- The General Availability release is 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 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 up to and including version 1.6.x, 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.
- Should a critical error be detected in a release during its Maintenance Period 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.
Version Support Period
Version Support is a service for enterprise customers that provides bug-fixes after the date of the Last Public Bug-fix Release up to the End of Life.
- 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
- Version Support provides enterprise customers with releases after the end of the Maintenance Period up to the End Of Life.
- Version Support maintains source code for all components of a Last Public Bug-fix Release incl. set-up procedures up to the End of Life.
- Should a critical error be detected in a Last Public Bug-fix 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.
- Charging model
- Such an individual service requires substantial effort and time from our side. We ask our customers to subscribe to this service in addition to Product Maintenance.
- 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 charged 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.