Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 35

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version 36

changes.mady.by.user Andreas Püschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For a detailed list of supported platforms see the FAQ: Which platforms is JobScheduler available for and what platform support is provided?

Version Support

Product Maintenance Period

Product Version Support is a service for enterprise all customers that provides bug-fixes for a specific product release stand for a period of up to two years after the General Availability releasestarting from the General Availability date up to the Latest Public Bug-fix Release.

  • Target Audience
    • SOS provides this service to all 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"with a support contract.
  • Scope
    • SOS Version Support Product Maintenance provides enterprise customers with releases for two years, starting from the general availability dateafter the General Availability date up to the end of the Maintenance Period.
    • The General availability 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 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 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 particular release Last Public Bug-fix Release incl. set-up procedures for the two year Version Support periodup to the End of Life.
    • Should a critical error be detected in a release 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, e.g. 1.7.3.
  • 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 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 charged in addition to the product maintenance 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.