You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 11
Next »
PCR will patch the last two versions of the application and the current LTS Release. Customers will continue to receive Help Desk Support for releases outside of the support period for a given release. Bug fixes are only released for versions that are actively supported.
Key
| Active support | A release that is actively supported. |
| End of life | A release that is no longer supported and will not receive bug fixes. Customers using one of these releases should upgrade as soon as possible. |
Version History
Release Types
| LTS Release | An LTS Release is a Major Release that PCR will support for 12 months. All other releases are supported for two release cycles. LTS Releases will be patched (as a hotfix) for any Critical or High Impact bugs applied after a release. These include (but are not limited to): service-impacting issues, billing issues, or charge-related bugs. These issues have no workaround, or the workaround is cumbersome. LTS Releases are intended to relieve “Upgrade Fatigue” for Customers who may not need all of the latest features but need critical bugs fixed. Once the 12-month period has elapsed, PCR will work with customers to move them to the next LTS release. |
| Major Release | Major releases consist of new features and some bug fixes. These features have a relatively large scope with a greater impact on development and testing, e.g. Accounts Receivable, Service Desk Archiving, Work Order, etc. There will be three feature & bug-fix releases in a given year. |
| Minor Release | Minor releases consist mostly of bug fixes and occasionally minor enhancements to the application. Minor enhancements are relatively small changes with a low impact on development and testing, e.g. adding a column to a grid, a new field, or tweaking the API. The specification process will occur in at least the month prior to being assigned. The specification process will occur in tandem with the traditional development and testing cycle. |
Archived Releases No Longer Supported
